Incompatibility with numpy 2.0.0 -> error on import

Importing QOI package while having Numpy 2.0.0 installed causes this error:
Traceback (most recent call last):
  File "D:\...\MultiScaler-Plus\src\standalone.py", line 14, in <module>
    import qoi
  File "C:\Users\...\AppData\Roaming\Python\Python312\site-packages\qoi\__init__.py", line 2, in <module>
    from qoi.qoi import QOIColorSpace, decode, encode, read, write
  File "src/qoi/qoi.pyx", line 1, in init qoi.qoi
ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject

Thanks, verified. Looks like numpy 2 is release as of a week ago, and these release notes look pretty relevant!

I'll have a quick look at how scipy does things (which is where most of my setup.py is copied from).

Cool, v0.7.0 should now support numpy>=2.0.0 (and older versions). Once the github action has run (assuming it succeeds), it should publish - can you check? Thanks.

Neat!
Thanks a lot!
Have a nice day :)

Older Numpy still works with no issues, newer does not crash on QOI import but crashes on different package import...
Time to make a new issue on different repo :/
Thanks for quick response!
Have a nice day! 😺

Found the new culprit: Torch
Issue already there, just have to wait.


Learn how to modify Sidebar of Wiki

Learn how to modify Sidebar of Wiki and create one.

Here is a useful link.

Sidebar is created and contents are arranged.


Update hooks.md with multiple component selector

Hi, I got a little confused when reading about this code... I believe the makeSelectCompletedTodosCount here is the selector factory, and selectCompletedTodosCount is a selector instance created by the factory.
LMK if my understanding is wrong.

Appreciate the PR, but the current code is correcct as-is - it's just abbreviating the usage here.
What we have now is:
const selectCompletedTodosCount = useMemo(makeSelectCompletedTodosCount, [])

useMemo accepts a callback function (kind of like another "factory" in a sense). It will call back and save the return value for later use.
Here, we're passing makeSelectCompletedTodosCount as the "factory" directly to useMemo.
This is exactly the same as if we wrote:
useMemo(() => {
  return makeSelectCompletedTodosCount()
}, [])

We're just eliminating the outer arrow function that does nothing except call makeSelectCompletedTodosCount.
If we did this:
useMemo(makeSelectCompletedTodosCount(), [])

we would actually be calling makeSelectCompletedTodosCount too early, and passing the new selector function as the argument to useMemo, which wouldn't be correct.


[Feature] Add document for environment_variables and Audit all environment variables to identify which should not be modified by users.

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Add a document for environment_variables and Audit all environment variables to identify which should not be modified by users.
FQ_RAY_IP
RAY_IP
RAY_CLUSTER_NAME
RAY_PORT
RAY_ADDRESS
RAY_USAGE_STATS_KUBERAY_IN_USE
REDIS_PASSWORD
RAY_EXTERNAL_STORAGE_NS
// Only add this env for Ray Service cluster to improve service SLA.
RAY_TIMEOUT_MS_TASK_WAIT_FOR_DEATH_INFO
RAY_GCS_SERVER_REQUEST_TIMEOUT_SECONDS
RAY_SERVE_KV_TIMEOUT_S
SERVE_CONTROLLER_PIN_ON_NODE
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

CLUSTER_DOMAIN: https://github.com/ray-project/kuberay/pull/951

REDIS_PASSWORD: https://github.com/ray-project/kuberay/pull/986


chore: generalize CODEOWNERS to use whole-team instead of web-specific team

Description of changes
We've started updating all the accessibility insights repos to use a shared CODEOWNERS team, rather than maintaining separate ones per project. This brings axe-sarif-converter up to date with this new policy.
Pull request checklist

[x] PR title respects Conventional Commits (starts with fix:, feat:, etc, and is suitable for user-facing release notes)
[x] PR contains no breaking changes, OR description of both PR and final merge commit starts with BREAKING CHANGE:
[n/a] (if applicable) Addresses issue: #0000
[n/a] Added relevant unit tests for your changes
[n/a] Ran yarn precheckin
[n/a] Verified code coverage for the changes made

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Is it possible to use warp-ctc instead?

The benchmark in https://github.com/baidu-research/warp-ctc is much faster than eesen's implementation.

We are studying the validity of the comparisons they presented, specifically the linear correlation between time and N for Eesen.

Parallelization is still an issue for eesen, which needs to be addressed
if it is be used massively.
X.
在 2016/1/18 23:37, Yajie Miao 写道:

We are studying the validity of the comparisons they presented,
specifically the linear correlation between time and N for Eesen.
—
Reply to this email directly or view it on GitHub
https://github.com/srvk/eesen/issues/28#issuecomment-172563775.

Any news/results about it?

We've looked at it, and it does not seem to be that straightforward. Baidu's code is only CTC (no LSTM) so one would need to put a few more things in place before it'll be usable. We also had difficulty understanding the published comparisons. Yajie, I know you're traveling - maybe you could comment some more?


PesterInterface is not Set-Strictmode v3 Safe

.IsRoot tests may fail because not all objects it tests have .IsRoot as a property

This is unfortunately more than just an inconvenience.  I spent many hours trying to figure out why my tests were not working within the VSC Adapter but were otherwise working with Invoke-Pester.  Please consider that any code being sourced to place under test that includes setting strict mode will cause the tests to fail within VSC.
Here is a minimal test case:
BeforeAll {
	Set-StrictMode -Version Latest
}

Describe 'Tests' {
	It 'Should-Pass' {
		# This test should pass.
	}
}

@JustinGrote,
Thanks for linking this case.

as strictmode doesn't really provide much benefit other than a lot more annoying runtime errors

I don't fully agree with this statement as it has helped me quiet some time with revealing simple typo's. Besides (just) for my tests I prefer to be as strict as possible as others who do use my scripts might have this simply switched on (as what in fact happens here)...

@iRon7 understood, I was just explaining why it is this way today, but I certainly underestimated the number of people using strictmode (as well as didn't think it would even matter due to the nature of how pesterinterface works).

@iRon7 Can you test with the latest prerelease? I've run strict mode both in the Extension Terminal and in the standalone runner and your minimal test case now works fine.

@JustinGrote,

Can you test with the latest prerelease?

I will try to find sometime this coming weekend.

From my perspective - both with the minimal test case included above, and with the tests that I've previously referenced at https://github.com/ziesemer/ad-privileged-audit/ - this is now working perfectly.  Thank you!

Glad to hear, will close but can reopen if a test case comes up that doesnt work.

Confirmed: prerelease version v2023.6.2 works fine now.
Thanks for the efforts


Revoked certificates not being decoded

Details about revoked certificates are not being properly decoded using the RFC 5280 API. No matter the contents of a CRL, the result always contains revokedCertificates: {}.

Fixed by yourself :wink:


Add slide style customization slot

This adds a new slide customization slot for styles!  I couldn't find where the docs at https://yet-another-react-lightbox.com/customization were stored, but those would need to be updated too.

[x] I have followed the 'Sending a Pull Request' section of the contributing guide

Can you give me an example of how this customization slot will be used? The idea behind customization slots was to provide an easy way to customize the default styles of visual elements (e.g. backdrop color, buttons styles, etc.)

My use case with this was to adjust the flexbox configuration of the slide, to change flexDirection to column in order to change some parts of how the caption description is displayed relative to the slide. I've accomplished it in my current project with CSS class overrides, but thought this would be a good addition to the first-class customization slots and fit with the others.
If you think this is too niche/doesn't fit, feel free to close this; it just seemed to be missing from the other available slots.  IMO, additional configuration is always a good option

Here's an example of what I did, where the `slide` needed `flex-direction: column` to make the caption description appear below the image, rather than on top of it

Thank you for providing these additional details. This is very helpful.

Thank you for your contribution!


Error: Cannot find module 'q'

$ taco run ios
ERROR running one or more of the platforms: Error: Cannot find module 'q'
You may not have the required environment or OS to run this project
$ node -v
v4.2.6
$ taco -v
1.2.0
$ cordova -v
6.0.0
I'm using Mac
Created app with "cordova create"

Nevermind I need it to remove cordova-plugin-livereload


wp-config.php

WP-CLI writes the network constants to the end of wp-config.php. These need to be in config/application.php instead. A shell script will be need to correct this.
Note that after moving these constants, subdirectory installs work for multisite installs with only the main site listed in site_hosts.

No shell script needed. Manual entry of these in conjunction with a properly written play solved the issue.


Sync atbash-cipher

[x] Run bin/configlet sync -u -e atbash-cipher --yes --docs --filepaths --metadata --tests include (updates the Markdown files and maybe tests.toml)

docs: instructions unsynced: atbash-cipher

[x] Drop strict types comments from test file and example code (these are useless)
[ ] Add and sync test meta data to tests (uuid / @testdox in DocBlocks)
[ ] Decide on adding / adjusting / ordering test cases to match current problem specs

Do not redesign the student's interface or add test cases that would invalidate existing community solutions. These are extra tasks, which should be discussed in advance.

the decode() is currently not implemented in example.php so the missing test cases (all for decode()) is logically failing.
Should decode() be added to the example.php or left out from the tests?

About adding decode: Yes, I think that is worth breaking all existing solutions. @homersimpsons Do you agree?

There are 128 published solutions. So yes let's add decode.


Show warning if different TTL for records with same name + type

As per #74, we should show a warning if trying to "Apply" where records of same name and type has different TTL's.
For example;
example.com IN NS 3600 ns1.example.com
example.com IN NS 86400 ns2.example.com

Should yield a warning. Currently one of the records would be deleted when hitting "Apply".

#74 fixes this. That is, no warning is shown, but it doesn't delete records anymore.


[Bug]: Cannot import from ts-gaussian even thought the build runs fine

Version
27.0.5
Steps to reproduce
I documented the whole thing with minimal reproduction github example on SO:
https://stackoverflow.com/questions/69428538/jest-cannot-run-tests-in-angular-package-format-project-with-ts-gaussian-import
Expected behavior
Also documented in the SO
https://stackoverflow.com/questions/69428538/jest-cannot-run-tests-in-angular-package-format-project-with-ts-gaussian-import
Actual behavior
Also documented in the SO question:
https://stackoverflow.com/questions/69428538/jest-cannot-run-tests-in-angular-package-format-project-with-ts-gaussian-import
Debug log
● Test suite failed to run
Cannot find module 'ts-gaussian' from 'src/lib/demo.spec.ts'

> 1 | import { Gaussian } from 'ts-gaussian';
    | ^
  2 | const distribution = new Gaussian(0, 1);
  3 | test("gaussian", ()=>{
  4 |     expect(true).toBeTruthy()

  at Resolver.resolveModule (../../node_modules/jest-resolve/build/resolver.js:322:11)
  at Object.<anonymous> (src/lib/demo.spec.ts:1:1)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        1.99 s
Ran all test suites.
Temp/tsgaussian-demo $ export TS_JEST_LOG=ts-jest.log
Temp/tsgaussian-demo $ npm test

<EMAIL_ADDRESS>test
cd projects/demo && npx jest

FAIL  src/lib/demo.spec.ts
● Test suite failed to run
Cannot find module 'ts-gaussian' from 'src/lib/demo.spec.ts'

> 1 | import { Gaussian } from 'ts-gaussian';
    | ^
  2 | const distribution = new Gaussian(0, 1);
  3 | test("gaussian", ()=>{
  4 |     expect(true).toBeTruthy()

  at Resolver.resolveModule (../../node_modules/jest-resolve/build/resolver.js:322:11)
  at Object.<anonymous> (src/lib/demo.spec.ts:1:1)

Additional context
The test in running in an Angular Library Project
Environment
Need to install the following packages:
  envinfo
Ok to proceed? (y)

  System:
    OS: macOS 11.6
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 16.2.0 - ~/.nvm/versions/node/v16.2.0/bin/node
    npm: 7.13.0 - ~/.nvm/versions/node/v16.2.0/bin/npm
  npmPackages:
    jest: 27.2.4 => 27.2.4

Hi, the error you are seeing is thrown by jest module resolution. This is outside of scope for ts-jest. You can either use moduleNameMapper or create your own Jest resolver to solve this.


Don't fail if artifact already exists [error 409]

Hello,
we have multi module Android project. For uploading AAR artifacts to Bintray we using bintray-release plugin, which uses the gradle-bintray-plugin under the hood. We have configured our multi module project the same way as the new AndroidX library, so each module has an independent version. Our CI is building every module every time even if nothing changed
script:
    - ./gradlew clean assembleRelease bintrayUpload -PbintrayUser=$B_USER -PbintrayKey=$B_KEY

so we don't want the unchanged artifact to upload. Everything works fine, except upload to the Bintray repo.
Current behavior:
Execution failed for task ':module-name:bintrayUpload'.
Could not upload to 'https://api.bintray.com/content/.../version/com/sygic/maps/module-name/version/module-name-version-sources.jar': HTTP/1.1 409 Conflict [message:Unable to upload files: An artifact with the path 'com/sygic/maps/module-name/version/module-name-version-sources.jar' already exists]
Expected behavior:
bintray {
    ...
    skipUploadIfExist = true // new option
}

Then convert the error to "just" warning and continue without fail.
Note:
As a workaround we currently using override = true, but it is not an ideal solution.

To be honest I didn't find that very useful. I would rather think about why do you try to upload something when nothing have changed.
I would update my pipeline so that I know 'nothing have changed, no need to upload'...

Hello @StefMa,
let me explain it a little bit more. This is our CI configuration file and bintray-release plugin configuration file. The independent modules versions are defined in the Gradle project file. The deploy stage is triggered only when the new global project tag is pushed to the remote.
Actually, I can't imagine how to manage the case: 'nothing has changed, no need to upload' directly on the CI. Store somewhere the versions diff? Store and compare commits? The simplest way for us is: The version already exists on target? Ok, skip the upload.
For me personally, the "skipUploadIfExist" make more sense than the existing "override" attribute. Who wants to replace an already published version? This can be very tricky and dangerous for target consumers.

What do you mean with

The deploy stage is triggered only when the new global project tag is pushed to the remote.

I assume that each new git tag is a new version, no?
I mean you will only create a new tag if you change your version name, right? And even if nothing have changed (inside the module/code) the new version can be published.

@StefMa  The project is multi-module, the git tag defines the global version of the project (used internally for the sample app versioning, which promotes all the modules in the project). Each module has an independent version of the global project version. For example:
git tag 1.0.0 - defines the global project version used in the sample app (it will change with any change of any module)

app-samples - use the git tag version, so now 1.0.0
module-search-1.0.0
module-browsemap-1.0.0
module-common-1.0.0
uikit-viewmodels-1.0.0
uikit-views-1.0.0
...

Now, for example, module-browsemap has changed to 1.1.0 and uikit-views to 1.0.1:

git tag 1.0.2
app-samples - 1.0.2 (used the git tag version)
module-search-1.0.0 - unchanged, this version already exist on target (bintray)
module-browsemap-1.1.0 - defined independently
module-common-1.0.0 - unchanged, this version already exist on target (bintray)
uikit-viewmodels-1.0.0 - unchanged, this version already exist on target (bintray)
uikit-views-1.0.1 - defined independently
...

Later, only the module-search has changed from 1.0.0 to 2.0.0:

git tag 1.1.0
app-samples - 1.1.0 (used the git tag version)
module-search-2.0.0 - defined independently
module-browsemap-1.1.0  - unchanged, this version already exist on target (bintray)
module-common-1.0.0 - unchanged, this version already exist on target (bintray)
uikit-viewmodels-1.0.0 - unchanged, this version already exist on target (bintray)
uikit-views-1.0.1 - unchanged, this version already exist on target (bintray)
...

New module added:

git tag 2.0.0
app-samples - 2.0.0 (used the git tag version)
module-navigation-1.0.0 - defined independently
module-search-2.0.0 - unchanged, this version already exist on target (bintray)
module-browsemap-1.1.0  - unchanged, this version already exist on target (bintray)
module-common-1.0.0 - unchanged, this version already exist on target (bintray)
uikit-viewmodels-1.0.0 - unchanged, this version already exist on target (bintray)
uikit-views-1.0.1 - unchanged, this version already exist on target (bintray)
...

Did you solve this problem? I am currently stuck on the same problem and don't like using the "override = true" option.

Did you solve this problem? I am currently stuck on the same problem and don't like using the "override = true" option.

Did you solve this problem? I am currently stuck on the same problem and don't like using the "override = true" option.

No 😞

Did you solve this problem? I am currently stuck on the same problem and don't like using the "override = true" option.

No 😞


Remove yardops in gemspec files, bump to 0.5.1

Yardopts is intentionally in the gemspec so that it is available when rubydoc.info builds the docs.


Add a 5 second grace period when stopping the bazooka containers

In order to fix spurious mongoldb data corruption which can occur with no grace.
The server component was also modified to listen to and handle the SIGTERM signal docker sends to containers when stopping them, to avoid blocking for the duration of the grace period before stopping.

:+1:


Updated translations from Phrase

Exported the most recent locale files from Phrase

@karthikbtf This is me exporting strings after copying the backend accession state translations over. We'll have to remember to keep them in sync if/when we decide we don't like the translations for any of them and ask for new ones.


add KeyMap for vi

This add a KeyMap for vi including basic editing and movement with support for insert and normal mode.
#6

This is the first PR in a series. Each PR will add additional features.

Thank you!


Allow to use optional modifier with factory

This currently fails:
$factory->define(Model_Contest::class, [
    'sponsor_id' => 'optional:factory|' . Model_Contest_Sponsor::class,
]);

SQL ends up trying to insert the value optional:factory into the sponsor_id column.
This has been observed with 84e9807.
:information_desk_person: Can we make the optional modifier work with factories?

3.x is now the only currently maintained series for anything but important fixes and security fixes.

Thanks for your interest though.


Set cursor to code when clicking on a function

When clicking on a function in the CodeNav window, it would be nice to set the cursor to the function in the text-editor so we can start typing without clicking again in the text-editor window.

Thanks for the suggestion! Finally took the time to cleanup and improved the selection code.


Update apache-conf.html

Fix apache config for web server in order for it to work.

Looks good to me, thanks!


Merge pull request #1 from google/master

just fixed a typo in new.dart
from: unde
to: under

I signed it, its under our company TRH Hosting.
:)

@SpivEgin Looks like either this repo is not maintained anymore or you need to sign it so it's tied to your github user.


virtio0 (required) not found in current config

I've got this problem creating an instance. It looks like an API incompatibility to me, but of course it can be my foolishness too.
ProxMox version: 5.1-41
Here's my terraform config:
provider "proxmox" {
  pm_api_url = "https://<IP_ADDRESS>:8006/api2/json"
  pm_user = "root@pam"
  pm_password = "<REDACTED>"
}

Here's the VM description:
resource "proxmox_vm_qemu" "test" {
  name = "node-20"
  desc = "tf description"
  target_node = "pve"

  clone = "centos-7-x8664-template"
  storage = "local-lvm"
  cores = 2
  sockets = 1
  memory = 2560
  disk_gb = 25
  nic = "virtio"
  bridge = "vmbr0"
  ssh_forward_ip = "<IP_ADDRESS>"
  ssh_user = "terraform"
  ssh_private_key = <<EOF
-----BEGIN RSA PRIVATE KEY-----
private ssh key terraform
-----END RSA PRIVATE KEY-----
EOF

  os_type = "centos"
  os_network_config = <<EOF
TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="dhcp"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="eth0"
DEVICE="eth0"
ONBOOT="yes"
EOF

  provisioner "remote-exec" {
    inline = [
      "ip a"
    ]
  }

  provisioner "proxmox" {
    action = "sshbackward"
  }
}

Here's the hardware configuration of the template:

And this is the logging output:
tfdebug.log
Cloning the template using the GUI works as expected.

Alright. I found out the template was created with the (default) SCSI disk, but a new template using VirtIO disk worked fine. So now this has become a feature request I guess.

I'm having the same problem here. Is there any workarround?


User endpoint authentication

Closes #408
This adds authentication to all of the user endpoints. This also updates the application to create a default admin user on startup of the backend via the mongo connector if an admin user does not exist in the current database. The functional tests have also been updated to adapt to this change.

Could we just merge main into the full_authentication_service branch? This PR is hard to review otherwise, and merging main in will fix it.

Could we just merge main into the full_authentication_service branch? This PR is hard to review otherwise, and merging main in will fix it.

Done


Implementing Connection#setStatementTimeout

Issue
Currently, the Connection#setStatementTimeout method  is a NO-OP (No Operation), meaning it lacks functionality. This poses a limitation for developers who require the ability to set a statement execution timeout for better control over query performance.
Proposal
Implementing the necessary logic to support statement execution timeouts.

I would love to work on this. Can you assign it to me

Sure, No one stops you :D

@jchrys  Kindly Check I have generated PR :)

Thanks for your patience. Let me check it soon :D


Set the git identity before patching

When using sleigh as a dependency it fails in the GitHub Actions pipeline with an error like this:
HEAD is now at 9c724c1a Merge remote-tracking branch 'origin/GP-2355_AARCH64_thunk_pattern' into patch
[2/9] Performing update step for 'ghidrasource-populate'
[3/9] Performing patch step for 'ghidrasource-populate'

Committer identity unknown

*** Please tell me who you are.

Run

  git config --global user.email<EMAIL_ADDRESS>  git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: empty ident name (for <runner@xxx>) not allowed
FAILED: ghidrasource-populate-prefix/src/ghidrasource-populate-stamp/ghidrasource-populate-patch

For now I just set it the same as in main.yml, but let me know if there should be some logic there. Perhaps it should only set the identity if there is none set globally or something...

For now I just set it the same as in main.yml, but let me know if there should be some logic there. Perhaps it should only set the identity if there is none set globally or something...

I don't see any harm in doing it unconditionally. What do you think @ekilmer?


[Analytics][Newsroom] event7 is triggered on secondary nav component (Desktop and Mobile View)

Priority: 2 - High
Steps to Reproduce

Navigate to https://main--accenture-newsroom--hlxsites.hlx.live
Click "Artificial Intelligence" or any clickable in the Secondary Nav Component

Expected Result:
event7 is not triggered
Actual Result
event7 is triggered
Resolution
Need to add id="header-topnav" in the nav tag

@ravkiran I think the attribute id="header-topnav" was not included for mobile viewports

fixed in https://github.com/hlxsites/accenture-newsroom/pull/284


Structure html

Nice job finding a workaround on the CSS when the root problem was difficult to identify.  Try to commit more frequent and meaningful messages.  Your commits should look like a check list of what you're accomplishing along the way. Overall good work consistently hitting MVP.


Add Camel Yaml in recommended tags

fixes #985
might be better to wait merge in main branch and a release for at least one of the extension:

https://github.com/camel-tooling/camel-lsp-client-vscode/pull/830
https://github.com/camel-tooling/vscode-camel-extension-pack/pull/58
https://github.com/camel-tooling/vscode-camelk/pull/971

I took the key of the CRD from: https://camel.apache.org/camel-k/1.7.x/apis/camel.html

the 3 mentioned extensions has been released with the new keyword, the search is finding them:

Thanks @apupier !! This is awesome :rocket:


Check sensitivity to starting parameters

I used this guidance to set the starting values for the parameters in the HMMs. Once we select a model, I think it will be valuable/important to demonstrate that our findings are robust to these initial values.

That document has some good advice for how to test many different starting values (section 5) to find the best ones


Linking fails building from source and using system protobuf

In v7.1 make cc fails when linking libortools with the following error message
/bin/ld: /usr/lib/: file not recognized: Is a directory
collect2: error: ld returned 1 exit status
make: *** [makefiles/Makefile.cpp.mk:179: lib/libortools.so] Error 1
when having set
UNIX_PROTOBUF_DIR = /usr
The reason is in this line (Makefile.third_party.unix.mk)
DYNAMIC_PROTOBUF_LNK = -L$(_PROTOBUF_LIB_DIR) -lprotobuf
which on my system becomes becomes
-L/usr/lib64/ /usr/lib/ -lprotobuf

Normally, it should be robust to this
_PROTOBUF_LIB_DIR = $(dir $(wildcard
$(UNIX_PROTOBUF_DIR)/lib*/libprotobuf.$L
$(UNIX_PROTOBUF_DIR)/lib*/libprotobuf.$L@
$(UNIX_PROTOBUF_DIR)/lib/*/libprotobuf.$L))
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mar. 2 juil. 2019 à 15:15, LesserBabka<EMAIL_ADDRESS>a
écrit :

make cc fails when linking libortools with the following error message
/bin/ld: /usr/lib/: file not recognized: Is a directory
collect2: error: ld returned 1 exit status
make: *** [makefiles/Makefile.cpp.mk:179: lib/libortools.so] Error 1
when having set
UNIX_PROTOBUF_DIR = /usr
The reason is in this line (Makefile.third_party.unix.mk)
DYNAMIC_PROTOBUF_LNK = -L$(_PROTOBUF_LIB_DIR) -lprotobuf
which on my system becomes becomes
-L/usr/lib64/ /usr/lib/ -lprotobuf
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1394?email_source=notifications&email_token=ACUPL3MNMJNZSYBSZUBX6TTP5NIH3A5CNFSM4H43V462YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G44HGZQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3JCX2XMVKDJZV76MRLP5NIH3ANCNFSM4H43V46Q
.

The problem is that _PROTOBUF_LIB_DIR will contain both /usr/lib64 and /usr/lib, but only the latter is prepended with -L.

and both contains a libprotobuf ?
They are the same ?
I guess we should use $firstword here.
Which platform are you using?
Thanks
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mer. 3 juil. 2019 à 09:17, LesserBabka<EMAIL_ADDRESS>a
écrit :

The problem is that _PROTOBUF_LIB_DIR will contain both /usr/lib64 and
/usr/lib, but only the latter is prepended with -L.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1394?email_source=notifications&email_token=ACUPL3NJIHZZHSYQVGERK7DP5RHBHA5CNFSM4H43V462YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZDQTXA#issuecomment-507972060,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3PDL7KAQ6T4F22A5GLP5RHBHANCNFSM4H43V46Q
.

Ahh, I see your point now. Yes, they both do, but that is probably wrong, I agree. The one I have installed by package manager is in /usr/lib and the other one is probably from installing or-tools before actually. I should remove the one installed by or-tools before as they are both protobuf-3.7.1.
Thanks!


Kivy master trying to use pygame instead of sdl2?

Versions

Python: 3.7
OS: MacOS High Sierra
Kivy: master
Kivy installation method: pip

Description
App won't run in my build env using master, 1.10.1 is fine and this error doesn't occur.
Code and Logs
/usr/local/bin/python3.7 /Users/John/Development/Git/ogleavetracker/optileave/main.py
[INFO   ] [Logger      ] Record log in /Users/John/.kivy/logs/kivy_19-02-10_52.txt
[INFO   ] [Kivy        ] v1.11.0.dev0, git-4905319, 20190210
[INFO   ] [Python      ] v3.7.1 (default, Nov  6 2018, 18:45:35)
[Clang 10.0.0 (clang-1<IP_ADDRESS>)]
[INFO   ] [Factory     ] 184 symbols loaded
[DEBUG  ] [Cache       ] register <kv.lang> with limit=None, timeout=None
[DEBUG  ] [Cache       ] register <kv.image> with limit=None, timeout=60
[DEBUG  ] [Cache       ] register <kv.atlas> with limit=None, timeout=None
[INFO   ] [Image       ] Providers: img_tex, img_imageio, img_dds, img_gif (img_pygame, img_pil, img_ffpyplayer ignored)
[DEBUG  ] [Cache       ] register <kv.texture> with limit=1000, timeout=60
[DEBUG  ] [Cache       ] register <kv.shader> with limit=1000, timeout=3600
[DEBUG  ] [Window      ] Ignored <pygame> (import error)
[CRITICAL] [Window      ] Unable to find any valuable Window provider.
pygame - ModuleNotFoundError: No module named 'pygame'
  File "/usr/local/lib/python3.7/site-packages/kivy/core/__init__.py", line 59, in core_select_lib
    fromlist=[modulename], level=0)
  File "/usr/local/lib/python3.7/site-packages/kivy/core/window/window_pygame.py", line 8, in <module>
    import pygame

[INFO   ] [MD          ] forked KivyMD version: 0.1.2
[DEBUG  ] [Text        ] Provider <pango> ignored by config
[DEBUG  ] [Text        ] Ignored <pygame> (import error)
[DEBUG  ] [Text        ] Ignored <pil> (import error)
[CRITICAL] [Text        ] Unable to find any valuable Text provider.
pygame - ModuleNotFoundError: No module named 'pygame'
  File "/usr/local/lib/python3.7/site-packages/kivy/core/__init__.py", line 59, in core_select_lib
    fromlist=[modulename], level=0)
  File "/usr/local/lib/python3.7/site-packages/kivy/core/text/text_pygame.py", line 12, in <module>
    import pygame

pil - ModuleNotFoundError: No module named 'PIL'
  File "/usr/local/lib/python3.7/site-packages/kivy/core/__init__.py", line 59, in core_select_lib
    fromlist=[modulename], level=0)
  File "/usr/local/lib/python3.7/site-packages/kivy/core/text/text_pil.py", line 7, in <module>
    from PIL import Image, ImageFont, ImageDraw

[CRITICAL] [App         ] Unable to get a Text provider, abort.

Process finished with exit code 1

You're using macosx, did you recompiled the kivy? Can you share the log of the compilation?
img_sdl2 don't even appear so something is wrong. We are now requiring SDL_Image 2.0.2 as a minimum so double check that?

Here is what I done.
iMac:~ John$ pip3 install --upgrade git+https://github.com/kivy/kivy Collecting git+https://github.com/kivy/kivy   Cloning https://github.com/kivy/kivy to /private/var/folders/cs/z8kmlcfx39v8t4wrsnvj5n5h0000gn/T/pip-req-build-fajlfa3x Requirement already satisfied, skipping upgrade: Kivy-Garden>=0.1.4 in /usr/local/lib/python3.7/site-packages (from Kivy==1.11.0.dev0) (0.1.4) Requirement already satisfied, skipping upgrade: docutils in /usr/local/lib/python3.7/site-packages (from Kivy==1.11.0.dev0) (0.14) Requirement already satisfied, skipping upgrade: pygments in /usr/local/lib/python3.7/site-packages (from Kivy==1.11.0.dev0) (2.2.0) Requirement already satisfied, skipping upgrade: requests in /usr/local/lib/python3.7/site-packages (from Kivy-Garden>=0.1.4->Kivy==1.11.0.dev0) (2.20.1) Requirement already satisfied, skipping upgrade: chardet<3.1.0,>=3.0.2 in /usr/local/lib/python3.7/site-packages (from requests->Kivy-Garden>=0.1.4->Kivy==1.11.0.dev0) (3.0.4) Requirement already satisfied, skipping upgrade: idna<2.8,>=2.5 in /usr/local/lib/python3.7/site-packages (from requests->Kivy-Garden>=0.1.4->Kivy==1.11.0.dev0) (2.7) Requirement already satisfied, skipping upgrade: certifi>=2017.4.17 in /usr/local/lib/python3.7/site-packages (from requests->Kivy-Garden>=0.1.4->Kivy==1.11.0.dev0) (2018.10.15) Requirement already satisfied, skipping upgrade: urllib3<1.25,>=1.21.1 in /usr/local/lib/python3.7/site-packages (from requests->Kivy-Garden>=0.1.4->Kivy==1.11.0.dev0) (1.24.1) Building wheels for collected packages: Kivy   Running setup.py bdist_wheel for Kivy ... done   Stored in directory: /private/var/folders/cs/z8kmlcfx39v8t4wrsnvj5n5h0000gn/T/pip-ephem-wheel-cache-31noj1_4/wheels/f1/e9/42/d7175156e34c35dee2757fe34aa9b6e75c262a0c912bbd33e7 Successfully built Kivy Installing collected packages: Kivy   Found existing installation: Kivy 1.10.1     Uninstalling Kivy-1.10.1:       Successfully uninstalled Kivy-1.10.1 Successfully installed Kivy-1.11.0.dev0 iMac:~ John$
Should I be doing something else? Pretty sure this is how I normally update kivy.

I don't see any compilation going on at all. Do you also have Cython installed?

I'm not not home to test on the iMac just now but 90% sure cythin 0.29 is installed on that machine.
I will check later and confirm here.

so I gave it another go, here is the pip install and pip freeze
iMac:~ John$ pip3 install --upgrade git+https://github.com/kivy/kivy Collecting git+https://github.com/kivy/kivy   Cloning https://github.com/kivy/kivy to /private/var/folders/cs/z8kmlcfx39v8t4wrsnvj5n5h0000gn/T/pip-req-build-87urdm7n Requirement already satisfied, skipping upgrade: Kivy-Garden>=0.1.4 in /usr/local/lib/python3.7/site-packages (from Kivy==1.11.0.dev0) (0.1.4) Requirement already satisfied, skipping upgrade: docutils in /usr/local/lib/python3.7/site-packages (from Kivy==1.11.0.dev0) (0.14) Requirement already satisfied, skipping upgrade: pygments in /usr/local/lib/python3.7/site-packages (from Kivy==1.11.0.dev0) (2.2.0) Requirement already satisfied, skipping upgrade: requests in /usr/local/lib/python3.7/site-packages (from Kivy-Garden>=0.1.4->Kivy==1.11.0.dev0) (2.20.1) Requirement already satisfied, skipping upgrade: urllib3<1.25,>=1.21.1 in /usr/local/lib/python3.7/site-packages (from requests->Kivy-Garden>=0.1.4->Kivy==1.11.0.dev0) (1.24.1) Requirement already satisfied, skipping upgrade: chardet<3.1.0,>=3.0.2 in /usr/local/lib/python3.7/site-packages (from requests->Kivy-Garden>=0.1.4->Kivy==1.11.0.dev0) (3.0.4) Requirement already satisfied, skipping upgrade: certifi>=2017.4.17 in /usr/local/lib/python3.7/site-packages (from requests->Kivy-Garden>=0.1.4->Kivy==1.11.0.dev0) (2018.10.15) Requirement already satisfied, skipping upgrade: idna<2.8,>=2.5 in /usr/local/lib/python3.7/site-packages (from requests->Kivy-Garden>=0.1.4->Kivy==1.11.0.dev0) (2.7) Building wheels for collected packages: Kivy   Running setup.py bdist_wheel for Kivy ... done   Stored in directory: /private/var/folders/cs/z8kmlcfx39v8t4wrsnvj5n5h0000gn/T/pip-ephem-wheel-cache-tosy8x6s/wheels/f1/e9/42/d7175156e34c35dee2757fe34aa9b6e75c262a0c912bbd33e7 Successfully built Kivy Installing collected packages: Kivy   Found existing installation: Kivy 1.10.1     Uninstalling Kivy-1.10.1:       Successfully uninstalled Kivy-1.10.1 Successfully installed Kivy-1.11.0.dev0 iMac:~ John$ pip3 freeze appdirs==1.4.3 buildozer==0.40.dev0 certifi==2018.10.15 chardet==3.0.4 colorama==0.4.0 Cython==0.29 docutils==0.14 dropbox==9.1.0 idna==2.7 Jinja2==2.10 jnius==1.1.0 Kivy==1.11.0.dev0 Kivy-Garden==0.1.4 Kodistubs==17.6.5 MarkupSafe==1.1.0 pexpect==4.6.0 ptyprocess==0.6.0 Pygments==2.2.0 pyjnius==1.1.3 python-for-android==0.7.1 requests==2.20.1 sh==1.12.14 six==1.11.0 typing==3.6.6 urllib3==1.24.1 virtualenv==16.1.0 iMac:~ John$
Looks the same as before, however it is now working as expected... very strange!
So as its working I'll close this issue off.


Wrong link in email

The link in the email needs to be HTTPS and it needs to only contain one slash after the domain for it to work.
The link I was sent was http://www.xerorobot.org:8001//users/confirm/ but it needed to be https://www.xerorobot.org:8001/users/confirm/

This has been fixed.  It was just the wrong path in the .env configuration file.


UI Refresh with updated dependencies

This is based on #122 adding a bit more clean up and polish to the UI

Closing this as the rebasing didn't do its job and the diff contains both #122's and this PRs change.


EECS-480 Fix for kalastatic/prototype/styleguide URL without index.html

Adds an index.html when they visit kalastatic/prototype/styleguide.

@RobLoach I don't really understand why this is necessary. Isn't it default browser behaviour when you visit a path without a file extension for it to serve an index.html if it exists?

It is, but on Pantheon for some reason, it wasn't appending a / at the end, resulting in broken relative links. This is what would happen...

You'd visit kalastatic/prototype/styleguide
A <img src="logo.jpg"> would then load in the browser as kalastatic/prototype/logo.jpg rather then the correct path of kalastatic/prototype/styleguide/logo.jpg

So, making sure there was a index.html at the end would make the browser load as kalastatic/prototype/styleguide/index.html, fixing the relative links. logo.jpg would then load as kalastatic/prototype/styleguide/logo.jpg

@RobLoach your reasoning is good, however won't that be the same for more than just the styleguide? Your solution is limited to just `($last_arg == 'styleguide')'. Should this be broader?

Going to close this.


Catalog and Basket: two Microservices or same Microservice

What are the factors that determines catalog and basket are separate microservices, instead of in the same microservice?
If both are in the same microservice, it can still be automony in dev, deploy, scale.
Please elaborate if possible.

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 19862882-c106-afa7-660e-ead3b5dd880a
Version Independent ID: fea4a2d6-8aa5-a400-4261-6098e76d362b
Content: Challenges and solutions for distributed data management
Content Source: docs/architecture/microservices/architect-microservice-container-applications/distributed-data-management.md
Product: dotnet
Technology: dotnet-ebooks
GitHub Login: @nishanil
Microsoft Alias: nanil

Hi @PingPongSet, that's a good question!
I could mention a few differences that make them qualify as separate microservices, but there could be a lot more, as usual, depending on the context:

They have a completely different set of requirements, so they could (should?) have different dev teams.
For catalog you can actually still split it further to:

Have a microservice to display the catalog pages that will be used for (a lot of) customers and
Another microservice to edit the catalog, that will be used by far-less internal users (orders-of-magnitude difference), so they will scale differently.

You can also expect that there will be much more users browsing the catalog than actually buying and using the basket, so then again, scaling will probably be different.
You could have catalog-editing microservices published in a restricted network, only available to company employees, but catalog-browsing microservices have to be facing the Internet.

So this are just a few sample conditions that point to them being separate microservices, probably enough to make the point.
Hope this helps.

Closing this issue now but feel free to comment, will reopen if needed.


feat: add optional stricter password requirements

Allow password length and character class checking.
closes https://github.com/influxdata/influxdb/issues/24856

@gwossum - the constant time feedback was really good, thanks for that!
@davidby-influx - I have small improvements for constant time harder inline.

I thought about this more and we don't need to worry about constant time since:

we're storing a secure cryptographic hash (bcrypt()) and comparing the cryptographic hash of the users input against the stored hash. So long as the cryptographic hashing remains strong, a timing attack doesn't get you anything (assuming we don't leak anything about it before the comparison)
I totally missed that the strength checks are happening after the compare password. In this case the timing of the strength tests are irrelevant since we already know the password (I suppose someone could deduce our strength algorithm, but there is no need to deduce, we tell people in the error message and you can read the code)

Sorry for the extra noise (that said, I'm glad we thought through it to make sure we didn't introduce a vulnerability).


I would appreciate If there is a demo

I would appreciate If there is a demo on how to use the lib.

Here is a small demo:
https://github.com/bungle/iresty/blob/master/libs/resty/route/middleware/reqargs.lua

@bungle thanks


Problems installing ChocolateyGUI on Windows 10

I think I have installed powershell in my Windows 10.

@ustcltx  Hmm, I see what the problem is.
Since you are using our MyGet Feed, it is looking for the PowerShell package at that same location, and the PowerShell package isn't mirrored onto that feed.  Now, although you already have PowerShell installed, Chocolatey itself doesn't know about it.
Do that following:
choco install powershell -y
which should attempt the PowerShell installation, taking the package from the Chocolatey.org feed.  This shouldn't actually install anything, but it will let Chocolatey know that PowerShell is installed.
Then run the installation command for ChocolateyGUI again.
Let us know how you get on.

it is really works! Thanks for your help!

Glad to hear it! :+1:


Fix: terminal font size not respecting system level font scale #97

The terminal font-size now respects the system level font-size and dynamically adjusts as the system level font scaling changes. (All tests passed.)

Thanks so much for the PR! This will soon be released in the next version.


Basically I would like an equivalent of stage.signals.clicked.add(function() {....}) that fires when my surface representation (e.g. surfaceRep) finishes loading instead of when the stage is clicked.

This problem was covered in #142


Adds Mahout VectorWritableConverter util from Twadoop

This is a migration of Pig + Mahout integration utility VectorWritableConverter from Twadoop.
Questions for reviewers:

How does the package organization look? Would you prefer I stick VectorWriatbleConverter directly into elephantbird.pig.util?
The unit tests for SequenceFileStorage are really slow.. One option might be to relegate these to ant target "test-slow", or perhaps "test-integration". Suggestions?

The SequenceFileStorage tests seem slow due to the infamous sleep(5000). If we use the internal pig, it'll fly.. we need to figure out how to push this patch upstream, it's not quite clean enough for the general case..
Apache Pig 9.2:
[junit] Running com.twitter.elephantbird.pig.util.TestProtobufWritableConverter
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 16.693 sec
[junit] Running com.twitter.elephantbird.pig.util.TestThriftNameWritableConverter
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 16.774 sec
[junit] Running com.twitter.elephantbird.pig.util.TestThriftNameWritableConverterCustom
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 16.693 sec
Our version of 9.2:
[junit] Running com.twitter.elephantbird.pig.util.TestProtobufWritableConverter
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.726 sec
[junit] Running com.twitter.elephantbird.pig.util.TestThriftNameWritableConverter
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.68 sec
[junit] Running com.twitter.elephantbird.pig.util.TestThriftNameWritableConverterCustom
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.687 sec

:-(((

Ok, read the patch. Looks good (and also, you are a madman!). We should update to Readme to indicate Mahout version compatibility, and a blurb about what this does.
In fact we should probably add a whole wiki page about how this stuff works.
We can do that as a separate commit.
I'll merge it in.


Request docs changes: rootless installation

File: engine/security/rootless.md
https://github.com/docker/docker.github.io/blob/1976c2178c6317400fdbdc0933570c5ef9248ab6/engine/security/rootless.md

To install Rootless Docker as the "ROOT" user, see the Manual installation steps.

But the purpose of this page is installation without root privilege...

Manual installation (https://docs.docker.com/engine/security/rootless/#manual-installation)

Seems a placeholder, people don't know how to manually install without dig https://get.docker.com/rootless

It's better to provide the Uninstallation as the complement. This will make user more confident about the installation.

https://github.com/docker/docker.github.io/pull/12234 contains guide for uninstallation


ripes: 2.2.6-unstable-2024-04-02 -> 2.2.6-unstable-2024-04-04

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for ripes is: A graphical processor simulator and assembly editor for the RISC-V ISA
meta.homepage for ripes is: https://github.com/mortbopet/Ripes
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-04-04 in filename of file in /nix/store/gvz7j235js1jr4nnkv562rzfr5wbd1qy-ripes-unstable-2024-04-04

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
ripes

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gvz7j235js1jr4nnkv562rzfr5wbd1qy-ripes-unstable-2024-04-04 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ripes https://github.com/r-ryantm/nixpkgs/archive/ab497e0a5f03ab9c4c02327a66f7c4a2bf2ff747.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ab497e0a5f03ab9c4c02327a66f7c4a2bf2ff747#ripes

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gvz7j235js1jr4nnkv562rzfr5wbd1qy-ripes-unstable-2024-04-04
ls -la /nix/store/gvz7j235js1jr4nnkv562rzfr5wbd1qy-ripes-unstable-2024-04-04/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

ripes

Maintainer pings
cc @wineee for testing.

not sure if this is the place to mention this @wineee
but seems like either this is not in the binary cache or failing to build on darwin due to some recent update.
error: builder for '/nix/store/jpabpi6ld7chpshbv9xiiba3564kvmhx-ripes-2.2.6-unstable-2024-04-04.drv' failed with exit code 2;
       last 25 log lines:
       > /tmp/nix-build-ripes-2.2.6-unstable-2024-04-04.drv-0/source/external/VSRTL/external/Signals/Delegate.h:805:15: warning: unused typedef 'ERROR_CantUseEvilMethod' [-Wunused-local-typedef]
       >   805 |                 typedef int ERROR_CantUseEvilMethod[sizeof(GenericClass *)==sizeof(function_to_bind) ? 1 : -1];
       >       |                             ^
       > /tmp/nix-build-ripes-2.2.6-unstable-2024-04-04.drv-0/source/external/VSRTL/external/Signals/Delegate.h:820:15: warning: unused typedef 'ERROR_CantUseEvilMethod' [-Wunused-local-typedef]
       >   820 |                 typedef int ERROR_CantUseEvilMethod[sizeof(UnvoidStaticFuncPtr)==sizeof(this) ? 1 : -1];
       >       |                             ^
       > 8 warnings generated.
       > /tmp/nix-build-ripes-2.2.6-unstable-2024-04-04.drv-0/source/external/VSRTL/external/Signals/Delegate.h:202:14: warning: unused typedef 'ERROR_CantUseHorrible_cast' [-Wunused-local-typedef]
       >   202 |         typedef int ERROR_CantUseHorrible_cast[sizeof(InputClass)==sizeof(u)
       >       |                     ^
       > /tmp/nix-build-ripes-2.2.6-unstable-2024-04-04.drv-0/source/external/VSRTL/external/Signals/Delegate.h:319:16: warning: unused typedef 'ERROR_Unsupported_member_function_pointer_on_this_compiler' [-Wunused-local-typedef]
       >   319 |                 typedef char ERROR_Unsupported_member_function_pointer_on_this_compiler[N-100];
       >       |                              ^
       > /tmp/nix-build-ripes-2.2.6-unstable-2024-04-04.drv-0/source/external/VSRTL/external/Signals/Delegate.h:805:15: warning: unused typedef 'ERROR_CantUseEvilMethod' [-Wunused-local-typedef]
       >   805 |                 typedef int ERROR_CantUseEvilMethod[sizeof(GenericClass *)==sizeof(function_to_bind) ? 1 : -1];
       >       |                             ^
       > /tmp/nix-build-ripes-2.2.6-unstable-2024-04-04.drv-0/source/external/VSRTL/external/Signals/Delegate.h:820:15: warning: unused typedef 'ERROR_CantUseEvilMethod' [-Wunused-local-typedef]
       >   820 |                 typedef int ERROR_CantUseEvilMethod[sizeof(UnvoidStaticFuncPtr)==sizeof(this) ? 1 : -1];
       >       |                             ^
       > make[1]: *** [CMakeFiles/Makefile2:990: external/VSRTL/graphics/CMakeFiles/vsrtl_gfx_lib.dir/all] Error 2
       > make[1]: *** Waiting for unfinished jobs....
       > 8 warnings generated.
       > [ 57%] Linking CXX static library libassembler_lib.a
       > [ 57%] Built target assembler_lib
       > make: *** [Makefile:136: all] Error 2
       For full logs, run 'nix log /nix/store/jpabpi6ld7chpshbv9xiiba3564kvmhx-ripes-2.2.6-unstable-2024-04-04.drv'.

I might be doing something totally wrong so please let me know.

Sorry, I don't use darwin and can't help

Sorry, I don't use darwin and can't help

@winee thx for the reply, can you give me a pointer on who should i ping about this.
happy new year btw


Mosek license file can no longer be found after #2326

Describe the bug
Setting MOSEKLM_LICENSE_FILE in the current processes environment prior to using cvxpy no longer works.
To Reproduce
import os

from cvxpy.tests.solver_test_helpers import StandardTestLPs

os.environ['MOSEKLM_LICENSE_FILE'] = '/path/to/mosek.lic'
StandardTestLPs.test_lp_0(solver='MOSEK')

Expected behavior
I expect the code above to continue working.
Output
This now raises:
mosek.Error: rescode.err_missing_license_file(1008): License cannot be located. The default search path is ':/home/user/mosek/mosek.lic:'

See: #2326

@apmorton which mosek and cvxpy version are you using?

mosek 10.1.31
cvxpy 1.5.1

In Mosek 10 with the global environment the path to the license file must be known before the first time Mosek is loaded. So an easier hack would be to first set the variable in os.environ and then "import mosek", or in any case set the environment before the first import of anything from mosek, cvpy etc. that could call Mosek. I don't guarantee it works on Windows.
The only true and correct solution of course is to never change the environment inside the process but set everything before calling the process.

Thanks @aszekMosek for the explanation, and glad that @apmorton found a workaround. Does not appear to be directly related to a change in CVXPY, so I'm going ahead and close this issue for now.

I'm not sure that is a fair assessment - this is the direct result of a change in cvxpy - #2326
Prior to then cvxpy wouldn't initialize mosek until the first usage, now it initializes it at import time.
This is a noticeable behavior change and broke our usage of cvxpy.
@aszekMosek is the workaround I posted above something supported by mosek?

@apmorton sorry about that, misread the issue to be a change in mosek behavior!

Both before and after #2326 CVXPY did not support any official mechanism to pass a license path to Mosek, so nothing changed in this respect. I would argue that both your solutions before and after #2326 are to some extent semi-supported hacks which one way or another try to bypass the one official mechanism applicable in this situation, which is to have MOSEKLM_LICENSE_FILE set in the initial environment of the process.
Yes, the workaround works because it is ultimately equivalent to calling the API method env.putlicensepath() on the global Mosek environment created when Mosek is first loaded. As of now it is not officially supported.
If you would like to then please contact Mosek support and we can think what else can be done about that.

We have been relying on the ability to set MOSEKLM_LICENSE_FILE path at runtime in production for many years.
The requirement to know this path and set an environment variable prior to process creation in all possible scenarios where mosek will be used is very tedious.
We will be reaching out to support on this matter since having the ability to set this at runtime is important to our business.

We have some idea for what we could change so that you get an official, supported solution, but that will be in Mosek version 10.2, ie. the current one. We can discuss it in support.
Just to summarize the other current options for how to modify the license path in the global Mosek environment:

your solution with mosek.Env(globalenv=True).putlicensepath("/path/...") (works, relies on unofficial behavior)
setting os.environ before the first time any mosek is loaded (Linux and OSX only, relies on unofficial behavior)
using Fusion as a proxy: mosek.fusion.Model.putlicensepath("/path/...") (works, official for the Fusion API, unnatural in the context of cvxpy)

The proposed solution we have in mind goes towards cleaning up and legalizing something along the lines of 1. Until you can use that then the solution in 1. is probably best.


The participant object is wrong in the Start a chat thread snippet

In the "Add a user as a participant to the chat thread" section sample the participants object is defined correctly as:
participants: [     {       id: { communicationUserId: '<NEW_PARTICIPANT_USER_ID>' },       displayName: 'Jane'     }   ]
BUT in the "Start a chat thread" section sample it is incorrectly defined as:
participants: [       {         id: '<USER_ID>',         displayName: '<USER_DISPLAY_NAME>'       }     ]
This returns an error!

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2a088bb9-e3ac-819c-8987-e1a27adfb603
Version Independent ID: e491ccd7-5e5d-d8b0-1aa8-51f2e15fd9e8
Content: Quickstart - Add chat to your app - An Azure Communication Services quickstart
Content Source: articles/communication-services/quickstarts/chat/get-started.md
Service: azure-communication-services
GitHub Login: @fanche
Microsoft Alias: mikben

@ichivers Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

Thanks for bringing this to our attention. The document has been updated to reflect the above correction. #please-close


Would you like to take the lead to https://github.com/Ynn/sd-webui-faceswap

I have developed a similar extension that i do not plan to maintain in the future. I have noticed that yours only recently. Would you like to restart from it. I could ask the automatic 1111 community to switch to your version of the extension ?

lol
I found your repo a couple of days ago and was thinking about doing the same and link to yours. :)
I wasn't really planning to work much on my version, it is just a minimal implementation to see if it would work at all. (And to be honest I wasn't going to release it first, just uploaded it to make it easier for me to install and hope that someone else would find it and make a "real" extension of it.)
If you really plan to drop your project, I'm ok with you linking to this one. But I can't promise I'll do much more than the current version.

roop as provided another option :)


[FEATURE] Delete models once synced

Being able to delete models once they are synced.

@schaitra can you please add a bit more information to the issue.


Correct broken link

Summary
The contributing link was broken and is now fixed. The CLA link is also broken, and so I have not signed it... point me to it and I'll fix that as well if you like :)
Requirements (place an x in each [ ])

[X] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[X] I've read and agree to the Code of Conduct.

The following point can be removed after setting up CI (such as Travis) with coverage reports (such as Codecov)

[ ] I've written tests to cover the new code and functionality included in this PR.

The following point can be removed after setting up a CLA reporting tool such as cla-assistant.io

[ ] I've read, agree to, and signed the Contributor License Agreement (CLA).

Just a reminder that I need someone to point me to the right CLA link so I can sign it.

Thanks for flagging this. We have fixed the link issues.


Fix spacing on H4s

They need to have more space above and less below:
http://opennews.mofostaging.net/blog/nicar/

fixed with #243


Shadow container

Implements #470

 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.

also, forgot to mention you will have to adhere to: www.conventionalcommits.org

all should be good now :)

@kazo0 conflicts fixed!

@roubachof I believe the remaining CI failures should be fixed after you upgrade SkiaSharp to 2.88.3 or later

/azp run

I upgraded to SkiaSharp 2.88.3 to tackle a wasm script issues, but it seems it made tests failed for some reasons...

it seems that updating to 2.88.3 to resolve the emscript issue caused by 2.88.2 on CI induced this exception on Android:
[monodroid] JNIEnv.FindClass(Type) caught unexpected exception: Java.Lang.ClassNotFoundException: crc641bba16f87fb10160.SKXamlCanvas ---> Java.Lang.ClassNotFoundException: Didn't find class "crc641bba16f87fb10160.SKXamlCanvas" on path: DexPathList[[zip file "/data/app/~~jJG9QmxuVQK6BHk5FQYOeQ==/uno.platform.toolkit-uFmXBuAHsA7MyJDUfnMz0A==/base.apk"],nativeLibraryDirectories=[/data/app/~~jJG9QmxuVQK6BHk5FQYOeQ==/uno.platform.toolkit-uFmXBuAHsA7MyJDUfnMz0A==/lib/x86_64, /data/app/~~jJG9QmxuVQK6BHk5FQYOeQ==/uno.platform.toolkit-uFmXBuAHsA7MyJDUfnMz0A==/base.apk!/lib/x86_64, /system/lib64, /system_ext/lib64]]
[monodroid]    --- End of inner exception stack trace ---
[monodroid]   at Java.Interop.JniEnvironment+StaticMethods.CallStaticObjectMethod (Java.Interop.JniObjectReference type, Java.Interop.JniMethodInfo method, Java.Interop.JniArgumentValue* args) [0x00068] in /Users/runner/work/1/s/xamarin-android/external/Java.Interop/src/Java.Interop/obj/Release/JniEnvironment.g.cs:12890
[monodroid]   at Android.Runtime.JNIEnv.FindClass (System.String classname)

@eriklimakc is this PR sill used ? If not, let's close it.


[Feature]: Add tap action to Title card

Requirements

[X] I have updated Mushroom to the latest available version
[X] I did a search to see if there is a similar issue or if a pull request is open.

Is your feature request related to a problem?
I have multiple views, and would love to navigate to another view by pressing the title card

Duplicate https://github.com/piitaya/lovelace-mushroom/issues/665


feature: auto generate of support yaml to include pvi

We have a nice auto generator to make support.yaml from builder.py files.
It's here: https://github.com/epics-containers/ibek/blob/main/builder2ibek.support.py
At present this does not add the pvi: dictionary into each device. It's not a builder thing but would be nice to have (but maybe I'm biased because I'm working on AreaDetector with its 40 or so devices - many support modules would have only 1).
The process could be:

use pvi to generate all of the *.pvi.device.yaml files in your ibek-support folder.
perhaps manually fix up those yaml
run builder2ibek.support.py to generate xxx.ibek.support.yaml but also point it at the *.pvi.device.yaml  so it can add the pvi: entries.

@coretl is this worth it? I'm currently maintaining an auto generation of the the support.yaml here and the pvi thing is breaking it - but once we have support.yaml fully done we can forget about converters really.

@GDYendell I think this comes down to how much the autogenerated pvi yaml files will have to change. If we can live in a world where ibek and pvi files are autogenerated for long enough for the syntax to settle, then we should add support to builder2ibek. We also need to think about what happens when we add a new record to a template, can we use the pvi converter to append to an existing pvi file?

Is there a way to tell in the convert which builder objects have a corresponding pvi yaml? I guess if there is a yaml file with the same name as the class it should use it?
Whether it is worth it also depends on https://github.com/epics-containers/pvi/issues/60


Can a substate transition to a sibling of its parent state?

Hey @davidkpiano,
Was simply wondering if this is even possible using the Statecharts formalism:
states: {
  foo: {
    states: {
      fooSub: { on: { EVENT: 'bar' } }, // when EVENT happens, go to the parent state 'bar'
    }
  },
  bar: {...}
}

Thanks,
Luca

Yep, makes sense. Also, I wouldn't worry about the redundancy of navigating to a child state because that would never occur - if a parent state has child states, it has an initial state (unless its child states are orthogonal), so it would be in its initial child state already - and then the other syntaxes apply.

Wait, what do you mean by "and then the other syntaxes apply"?  Concrete example:
{
  A: {
    on: { ONE: 'B',
            TWO: 'A.B' }
    initial: A
    states: {
      A: {}
      B: {}
    }
  },
  B: {}
}

This slightly confusing statechart has two states A and B, while A has two substates A.A and A.B.  The event ONE would unambiguously take it to state B (the root state B), while the event TWO would target the A.B state.  Moreover, I don't think xstate has the notion of internal or external events, so it would perhaps exit the root A state and enter A, then A.B (not the initial A.A).
Is this right?

Moreover, I don't think xstate has the notion of internal or external events

This is something I want to add soon - and it will probably come as a result of #43.
For the example above, to exemplify what I was saying:

Entering A necessarily enters A.A, so the current state is A.A

Note: it's impossible to be in state A without being in one of A's substates, per statechart semantics. A parent state with substates cannot be a leaf node state.

On ONE from A.A, the event is not handled from A.A, so it transitions from the parent to B
On TWO from A.A, the event also isn't handled, so (if we are deciding against relative/absolute state resolution steps in order to mitigate ambiguity), this will throw an ⚠ error ⚠  since A.A.B does not exist.

So if you want to transition to A.B, the configuration (given your table) should look like:
{
  A: {
    on: {
      ONE: 'B', // A.B
      TWO: '^B', // B
    },
    // ...
  },
  B: {}
}

I agree that when it Enters A, it also Enters A.A by default; however, when an event is declared in A, it should be resolved relative to A not relative to whatever deep state that might be active.
And I disagree with that (in my statechart) that TWO from A.A should end up looing for A.A.B, since the event is declared by the top level A state, not A.A.

Edited the above - resolved in the Gitter chat. @mogsie's interpretation is correct, and is how xstate currently works.

My two cents: I like the idea of being explicit (e.g. ^foo) rather than applying a magic resolution algorithm. However, I'm a bit worried about adding too much complexity (e.g. DSL).
I didn't know you were discussing on Gitter, I'll join and read more there :)
Thank you very much, everyone.

We weren't discussing on gitter until we discovered we were on-line at the same time, and it seemed as if we were talking past each other.  github ain't chat! :D

I am pretty new to this whole discussion about statemachines but after thinking of ways to solve the transition problem i asked myself if this wouldnt be solveable if the different states would have unique ids (smth. Seperate from the keys)
After experimenting i came to this idea:
js```
// State Constructors which generate a (hidden) unique id and take a string as state key
var yellow = state ("yellow");
var orange = state ("orange");
var red = state ("red");
Machine({
key: 'light',
initial: green,
states: [
// created states are setter functions
green({
on: {
TIMER: yellow
}
}),
yellow({
on: {
TIMER: red
}
}),
red({
on: {
TIMER: green
}
})
]
});

This would have the following advantages:

- no transition syntax needed
- explicit transitions
- transitions to any state possible
- functional composition of states

Of course this would be a major change, but maybe it would be worth it, long term :).

@katywings That's actually a pretty cool idea. Internally, it made me think of two things:

State nodes already have a (read-only) id property, so it might be useful if we could allow the developer to override that.
We should have some special syntax for targeting an absolute state by its id. The obvious one that comes to mind is #some.state.id.

By default, the state ID is the full path from its parent; e.g.:
{
  key: 'light',
  states: {
    green: {
      // equivalent to TIMER: 'yellow' in this case
      on: { TIMER: '#light.yellow' }
    },
    yellow: { ... }
  }
}

But you should be able to do this (in the future, maybe):
{
  key: 'light',
  states: {
    green: {
      id: 'green_a1b2c3-fake-uniqueid',
      // equivalent to TIMER: 'yellow' in this case
      on: { TIMER: '#yellow_a4b5c6-fake-uniqueid' }
    },
    yellow: {
      id: 'yellow_a4b5c6-fake-uniqueid',
      // ...
    }
  }
}

Which you could sugar with your above proposed functions (passed in as an object instead of an array, for consistency):
Machine({
  key: 'light',
  initial: green,
  states: {
    // created states are setter functions
    ...green({
      on: { TIMER: yellow }
    }),
    ...yellow({
      on: { TIMER: red }
    }),
    ...red({
      on: { TIMER: green }
    })
  }
});

Where green({ ... }) would return:
{ green: {
  id: 'green_a1b2c3-fake-uniqueid',
  // ... anything else passed in
  }
}

I'm wondering if the helper function for this would be best done in userland, though. But overriding ids might be a helpful feature.

This is now possible using the id prop, and id notation (e.g., #foo) above.


[Improvement][easyscheduler] Remove easy scheduler code

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Right now, there exist some code related to easy scheduler. e.g. in tools/initialize sql, it's better to remove this kind of code.
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I want take this task

Assigned to you.

now i am working on this, but i can't find the file you mentioned like  tools/initialize sql.
And when i search the project with easyscheduler word,
part of them are in upgrade/1.2.0_schema folder, that's looks like the upgrade sql when user upgrade version.
others are in the md file. some picture link like https://analysys.github.io/easyscheduler_docs_cn/images/decentralization.png.
So I'm not sure if I still need to do this task.

now i am working on this, but i can't find the file you mentioned like tools/initialize sql. And when i search the project with easyscheduler word, part of them are in upgrade/1.2.0_schema folder, that's looks like the upgrade sql when user upgrade version. others are in the md file. some picture link like https://analysys.github.io/easyscheduler_docs_cn/images/decentralization.png.
So I'm not sure if I still need to do this task.

Some code also exist in https://github.com/apache/dolphinscheduler/blob/9c8d1dc6d82f8c3f6db57c1a8a2f1ff6d2b7e00d/dolphinscheduler-tools/src/main/java/org/apache/dolphinscheduler/tools/datasource/DolphinSchedulerManager.java#L91


Add a mutex_map example

Fixes #128

I added an example showing how to use lazy_static for a mutable map. The only slightly weird bit is that I needed to change the Travis tests to not run the example for Rust 1.27.2. I notice that the doctests also don't run or pass for Rust 1.27.2, so I figured that would be the preferred solution.

Hey @LukasKalbertodt, do you know who could review this PR?


Raw 3d support

Initial 3d support per Chapter 13, not super clean.

Sorry, meant to create this on my own repo.


Add isdebug condition

add is debug condition to prevent run colouring in release mode if you forget to change it.

Added these through another change 👍


fix: Added missing attribute source_countries to ZIA zia_firewall_filtering_rule

Provide a general summary of your changes in the title above. You should
remove this overview, any sections and any section descriptions you
don't need below before submitting. There isn't a strict requirement to
use this template if you can structure your description and still cover
these points.
Description
Describe your changes in detail through motivation and context. Why is
this change required? What problem does it solve? If it fixes an open
issue, link to the issue using GitHub's closing issues keywords1.
Has your change been tested?
Explain how the change has been tested and what you ran to confirm your
change affects other parts of the code. Automated tests are generally
expected and changes without tests should explain why they aren't
required.
Screenshots (if appropriate):
Types of changes
What sort of change does your code introduce/modify?

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

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] This change is using publicly documented and stable APIs.

Codecov Report
Attention: Patch coverage is 11.11111% with 16 lines in your changes missing coverage. Please review.

Project coverage is 72.05%. Comparing base (45a003a) to head (d0190b3).

Files with missing lines
Patch %
Lines

zia/utils.go
0.00%
8 Missing :warning:

zia/resource_zia_firewall_filtering_rules.go
0.00%
7 Missing :warning:

zia/validator.go
0.00%
1 Missing :warning:

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #375      +/-   ##
==========================================
- Coverage   72.25%   72.05%   -0.20%
==========================================
  Files          82       82
  Lines       13910    13918       +8
==========================================
- Hits        10051    10029      -22
- Misses       3117     3152      +35
+ Partials      742      737       -5

Files with missing lines
Coverage Δ

zia/common.go
82.30% <100.00%> (ø)

zia/resource_zia_forwarding_control_rule.go
41.53% <ø> (-8.47%)
:arrow_down:

...resource_zia_fw_filtering_ip_destination_groups.go
64.33% <ø> (+1.39%)
:arrow_up:

zia/validator.go
33.09% <0.00%> (ø)

zia/resource_zia_firewall_filtering_rules.go
3.85% <0.00%> (ø)

zia/utils.go
43.47% <0.00%> (-1.98%)
:arrow_down:

... and 3 files with indirect coverage changes


Track the 0.2 release progress

This isn't a usual issue, but I needed a place to track the 0.2 progress.
The following is a list of steps that we will use to validate the 0.2 release:

[ ] 1. setup and run an authorized node: nodeA. one way or another we need to make sure we bootstrap the blockchain/transparency log, with at least a log that marks nodeA as authorized.

--> #1081 and #1082

[ ] 2. setup and run a regular node: nodeB
when it starts, it needs to be able to pull all existing blocks and make sure they get stored in the TransparencyLog DB

--> #833 - in progress (Xuefei)

[x] 3. trigger a build for a docker image:tag on nodeA

[x] 4. nodeA uses its configured build pipeline service to start a build and wait for the result

[x] 5. on nodeA: when the build is ready, nodeA creates a TPL and call add_payload on the Blockchain component (issue #1006 - PR #1042)

[x] 6. on nodeA: the blockchain needs to reach consensus with the other authorized nodes

--> I listed this step for completeness. We skip this in 0.2 - we use a 'light' consensus mechanism for now

[x] 7. on nodeA: the blockchain component makes sure the committed block is distributed across the Pyrsia network  -->  addressed by #978

[x] 8. on every other node in the network including nodeA: the blockchain component listens for new blocks and notifies listeners like the TransparencyLog component, which will in turn store the log in its DB. (issue #1007 - PR #1047)

[x] 9. on nodeB: do a docker pull of alpine:3.16

[x] 10. on nodeB: the artifact service finds a TPL for alpine:3.16 and requests the needed binaries from the p2p network (hence nodeA in this example)

[x] 11. on nodeB: the docker pull completes successfully

[x] 12. on any node: pyrsia inspect log docker --image image:tag outputs the transparency logs

[ ] 13. write down the acceptance criteria for 0.2 and ideally automate the testing of it

[ ] 14. make sure end-user and Pyrsia developer documentation are up-to-date

--> PR #1056

[x] 15. Take steps 9 to 12 on a node behind a NAT

Great this can be then converted into documentation for 0.2

For

setup and run an authorized node: nodeA. one way or another we need to make sure we bootstrap the blockchain/transparency log, with at least a log that marks nodeA as authorized.

Here are the steps I am thinking of

Run the k8s cluster - with Pyrsia nodes
Inject the authority key
Ensure the key is in the secure lockbox - may need to implement deploying the Vault
trigger a [9] action above and ensure that [6] consensus is reached.

@betarelease I intended step 1-3 to be implicit in the 'setup', but it's also fine to list them explicitly. What I meant with 'bootstrapping' is making sure we start off with at least some 'AddAuthorizedNode' transactions in the transparency log (and thus blockchain) for the authorized nodes.
In theory we could skip this in 0.2 but that would mean any node could act as an authorized node and perform builds.

I think adding the AddAuthorizedNode is good idea.
That makes me think - should we add a check somewhere in the blockchain code to ensure that only an Authorizednode is committing? and force that check everytime.

I think adding the AddAuthorizedNode is good idea.
That makes me think - should we add a check somewhere in the blockchain code to ensure that only an Authorizednode is committing? and force that check everytime.

Yes, according to the design of the blockchain, only AuthorizedNode can reach consensus, and only consensus members can commit blocks.

Acceptance criteria for 0.2 release

[ ] a central node is running, accepting bootstrap connections via boot.pyrsia.link
[ ] that central node initialized the blockchain
[ ] and it added itself as the first authorized node
[ ] a regular node bootstraps using boot.pyrsia.link by default, also behind a NAT router
[ ] and receives the existing blocks at start-up, storing the transparency logs in its local DB
[ ] an inspect-log for an existing Pyrsia artifact will succeed on the regular node
[ ] a Docker pull of an existing Pyrsia artifact will succeed
[ ] a Docker pull or an explicit build trigger, will send a build request to the central node
[ ] the central node listens for build requests and performs build using the build pipeline prototype
[ ] the regular node receives blocks (transparency logs) for newly added builds
[ ] the regular node can now inspect-log of the newly built artifact
[ ] the regular node can now pull the newly built docker image


handle equality conditions by e-graph lookup

@memoryleak47 If you happen to be bored, you can also look at how fact_srcs are parsed, and add the necessary code to parse the new "proven-by-egraph" facts. You would presumably need to add a new Source for this.


cli: Store parsed args in Homebrew.args and access @args everywhere else

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

https://github.com/Homebrew/brew/pull/3987#issuecomment-386190815

We could either do it this way or rename class var @args in global.rb to something else and replace occurences of Homebrew.args to the new name everywhere else

We could either do it this way or rename class var @args in global.rb to something else and replace occurences of Homebrew.args to the new name everywhere else

I think that would be preferable. How about @global_args?
Whatever we do: can you update brew bump-formula-pr in this PR to be consistent too? Thanks!

It feels really weird using a global variable Homebrew.args inside a CLI::Parser instance.

It feels really weird using a global variable Homebrew.args inside a CLI::Parser instance.

@reitermarkus What would you suggest instead?

Use
args = Homebrew::CLI::Parser.parse

instead of
@args = Homebrew::CLI::Parser.parse

everywhere. Then pass args to other methods that used @args before and use Homebrew.args to access global arguments.

@MikeMcQuaid which way should this be done ?
Both seem fine to me, with the implementation in this PR, its more like Homebrew.args is single source of truth, we can be sure args would be available in cross command module method calls, while with what @reitermarkus is suggesting we'd have to take care that args are passed around wherever required which I think might possibly lead to edge cases( or may be not too..)

I think might possibly lead to edge cases( or may be not too..)

I think there will be more edge cases (this PR included) the more global state there is.

@GauthamGoli Do you think if Homebrew.args is used only for global arguments it will be sufficient to only use e.g. @args (or args) in cmd/*.rb files? If so, I think that's the best solution and we can consider making things like --build-bottle global arguments (as they aren't specific to a single command). Thoughts?

brew info --build-bottle foo

should have interesting output.

should have interesting output.

@ilovezfs can you elaborate a bit on "interesting" 😉

Do you think if Homebrew.args is used only for global arguments it will be sufficient to only use e.g. @ args (or args) in cmd/*.rb files?

@MikeMcQuaid  Yes, all files except for update-report.rb , it has a Reporter class outside Homebrew module, we'd have to pass args when instantiating that.

@ilovezfs can you elaborate a bit on "interesting"

Presumably we want it to say --build-bottle isn't a valid option for info. But if --build-bottle is elevated to global status, I'm not sure how that's supposed to happen.

Presumably we want it to say --build-bottle isn't a valid option for info.

Exactly, otherwise what is the point in using an option parser? If it doesn't fail on invalid options, we could have just stayed with ARGV.include?.

Presumably we want it to say --build-bottle isn't a valid option for info. But if --build-bottle is elevated to global status, I'm not sure how that's supposed to happen.

Agreed. From that argument then --force and maybe even --quiet and --verbose shouldn't be global arguments either (as they don't do something for all commands).

@MikeMcQuaid Yes, all files except for update-report.rb , it has a Reporter class defined outside Homebrew module, we'd have to pass args when instantiating that.

This is fine. Alternatively we can consider moving it into the Homebrew module instead.

Should that still be using bump_args? https://github.com/Homebrew/brew/blob/master/Library/Homebrew/dev-cmd/bump-formula-pr.rb#L292


Hystrix 1.4.15 not available on Maven Central

Hystrix 1.4.15 release looks to be cut, but it's not available on Maven Central (search.maven.org)

Thanks for the report, @chrisgray .  I didn't change anything about the release process, so don't know what happened yet.  I'll investigate.

Problem also exists on Bintray: https://bintray.com/bintray/jcenter/com.netflix.hystrix%3Ahystrix-core/view.  Will get both resolved ASAP

Thanks for the quick turnaround!

This is now fixed and both download links on https://github.com/Netflix/Hystrix/releases/tag/v1.4.15 now work


In search of .NDA's hidden mass

I have delved into the depths of binary data extraction and have successfully found Active Mass, Remarks, and some other interesting data points for .nda files generated by Neware 4000 and 9000 instruments. I do not have access to .ndax files, so I cannot provide any information about those unfortunately.
NEWARE 4000 (and perhaps other machines)

The entered "Active Material" value exists at byte 0x00000098 (decimal: 152).

It appears that the data is stored in LE as a uint8 (BTS Software does not let you enter a negative number.)

The value decoded is actually the ActiveMaterial*1000 (in other words, to extract active material, divide this decoded value by 1000)

When specifying Active Material in BTS Software, the default is mg, but there are other options for units, including some volumetric types. I do not know how changing units affects this value.

The "Remarks" section exists at byte 0x0000090D (dec: 2317)

It is simply an ASCII/UTF-8 encoded string.

I suspect that it is 100 Bytes long, but this is untested.

NEWARE 9000

The same metadata type information is stored in the .nda files, but as a footer to the data, unlike the 4000 case.

I have identified the footer as beginning as a byte string of the following:
06 00 f0 1d 81 00 03 00   61 90 71 90 02 7f ff 00

This is used to signify the beginning to the header where our relevant metadata is stored.

I have seen this exact string in a few of my datafiles, but it is very possible that at least part of this string is not static, I just have not seen that case yet.

The first 107 bytes after the signifier are not decoded yet (and I have no plans to do so at the moment.)

The next 128 bytes are ASCII text for the "Creator" or "Operator"

The next 128 bytes are ASCII text for the "P/N"

The next 128 bytes are ASCII text for the "Remark Information" or "Comments"

The next 8 bytes are LE encoded double float for the "Active Material"

There is more in the footer following this, but it does not seem important to me at the moment. There is another big chunk of ASCII, so feel free to investigate at your interest.

Table of 9k Footer Storage Structure:
Bytes after signifier |dtype | data
1-107  |?     | Unknown
108-235|ASCII | Creator (Operator)
236-363|ASCII | P/n
364-491|ASCII | Remarks (Comments)
492-499|double| Active Material

I leave implementation details to the more experienced among us. I can certainly take a stab at adding some extraction code, as I plan on doing so for my personal work in the meantime. However, I don't know whether any of these extractions should be added to the main "read()" functions, or if they should be their own methods.
I can imagine extracting the mass and adding dedicated "Specific Capacity" Columns to the main read_nda() function. It is also possible to have some separate function along the lines of a "read_metadata()" function that returns a simple dictionary with Remarks, Active Material, P/N, Run Date, etc. as we find them. Either implementation would be valuable in my opinion.
There are a few other data structures that I have found in the Neware 4000 file format. In short, they aren't useful, so I wont provide too much detail. One instance is a data structure that extracts with the same format as the main data points, but it has a different identifier ('\xAA' instead of '\x55'). These data blocks appear to be the last data point of each step. Within these data blocks, there are 8 bytes of unidentified data that appear to be values for Differential Capacity.

Hey @AdamOpps , this is great, thanks for investigating. Do you have any of this implemented in code? I'll look through my internal nda/ndax files and see if this additional data shows up in the same places.

I started looking for active mass in some Neware 4000 files, and I think the number should be a 4-byte unsigned int. When I read 8 bytes, some of the files returned nonsense values. Can you check if 4 bytes still gives correct values for your files?
NewareNDA already returns some additional information via logging , so I'm thinking it's best to return active mass this way too. Otherwise there will need to be a new keyword argument, and I don't really want to get into post-processing.

4-byte unsigned integer is what I meant. Thanks for the clarification! I think I misread ImHex's data identifier and that Is what I quoted above.
I think putting the Active Material and Remarks into the log would be appropriate! I would advocate, however, for including columns for Specific Capacity directly into the returned dataframe from the read functions. If mass isn't specified, we could fill the column with zeros or NaNs or something. I doubt it would break compatibility for users with this solution. Let me know your thoughts though!

I created a new PR #59 for extracting active mass as logging information. I prefer this approach since many of my test files have an active mass of zero. For Neware 9000 I just looked for the mass bytes from the end of the file, but I only have 3 files to test. Can you check if this works on more files?

I gave it some tests, check out my comments! #59

#59 Code changes have been merged into development branch. Closing this issue for now, until any other breakthroughs are found!


Default CmpItemKind%name% to CmpItemKind

Reading the doc it seemed I could set CmpItemKind to override all item kind. Am I missing something?

it makes sense to me.


Bug: Wrong parameter used

Hi,
I'm debugging why my given memory limit is not being applied in the adapter. Looks like there is a bug in the MemoryOptions. I think preg_match in this line
https://github.com/laminas/laminas-cache-storage-adapter-memory/blob/d2c357a8b839ceb0e0781d5e9aebe46642dbf0b2/src/MemoryOptions.php#L88
should use the parameter $value instead of ini_get('memory_limit')?
BR,
Alex

Introduced in time immaterial by https://github.com/laminas/laminas-cache-storage-adapter-memory/commit/b87cc7469eedc691138142e55a1c20c16cf49221
There are no tests whatsoever for options object.
@leuchtdiode It would be great if you introduce them.
For this problem ini_set/ini_get is not needed. Test that:

call to setMemoryLimit() with invalid value like 'M128' produces exception with message containing "Invalid memory limit".
call to setMemoryLimit() actually sets it.

I just created a pull request, but there are some issues with my formatting. Do you have a code style XML somewhere for PHPStorm which I can use?
Furthermore I added these tests:
[ 'G1024', 1024 ]```

as valid ones. In my opinion they should raise a InvalidArgumentException as well. What do you think?

Do you have a code style XML somewhere for PHPStorm which I can use?

There's a PHPCS configuration at the root of the repository:  https://github.com/laminas/laminas-cache-storage-adapter-memory/blob/d2c357a8b839ceb0e0781d5e9aebe46642dbf0b2/phpcs.xml#L1-L20

as valid ones. In my opinion they should raise an InvalidArgumentException as well. What do you think? Which values do we want to allow? Only integers and "G", "M" and "k" as suffix, right? If so, I could adapt the regex and the tests.

Worth discussing on the PR directly :)


Update newest (no deep diff)

Description
Changes
Known Issues
Notes
Checklist

[ ] My name is on the list of contributors (CONTRIBUTORS.md) in the pull request source branch.
[ ] I have updated the documentation to reflect my changes.
[ ] My code changes have been verified by automated tests and pass all relevant test scenarios.

I just realized, that we may get a number of false positive equal_shallow and equal_deep calls.
The API adds info to nodes, like created_at etc. and these don't actually mean a diff, but will trigger a patch in the current design.
I don't think that is an issue, but something to keep in mind, and maybe for optimization later.


Update whats-new-windows-10-version-1809.md

Added a note for Web sign-in

file diff:
- non-ADFS federated providers (e.g.SAML).
+ credentials not available on Windows (e.g. Temporary Access Pass). Going forward, Web sign-in will be restricted to only support Azure AD temporary access pass.


No results from parsing

Hi, does your project still work? I tried on my files but I don't get any info about open tabs as in your example

$ python Chromagnon/chromagnonSession.py Current\ Session
SetWindowType - Window: 1, Type: 0
SetTabIndexInWindow - Tab: 2, Index: 0
SetPinnedState - Tab: 2, Pinned: 0
SetTabWindow - Window: 1, Tab: 2
SetSelectedTabInIndex - Window: 1, Index: 0
SetWindowBounds3 - Window: 1, x: 0, y: 23, w: 1680, h: 1023, State: 1
SetSelectedNavigationIndex - Tab: 2, Index: 0
UpdateTabNavigation - Tab: 2, Index: 0, Url: chrome://newtab/
SetSelectedNavigationIndex - Tab: 2, Index: 0
UpdateTabNavigation - Tab: 2, Index: 0, Url: chrome://newtab/
SetWindowBounds3 - Window: 1, x: 0, y: 23, w: 1680, h: 1023, State: 1
SetWindowBounds3 - Window: 1, x: 0, y: 23, w: 1680, h: 1023, State: 1

thank you
david

I also interested in results. And I want to port it to C# code.
Found such parser: https://github.com/deactivated/python-snss/blob/master/snss/init.py
Hopefully, it will be helpful for you guys! Let me know if you have any updates for me.


Convert strikethrough text

Convert strikethrough text in a Doc to ~~strikethrough~~ in Markdown and <del>strikethrough</del> in HTML.

This would be great. Right now the add-on seems to miss this –converting strikethrough text to HTML–.
Thanks!

This is great news. Thanks for a great and useful app

Strikethough text seems to be operating properly as of today's new version. Please reopen this bug if not.


Com enhancement

Minor update to improve usability

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

Project coverage is 34.54%. Comparing base (ddb5cf0) to head (6255797).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4393      +/-   ##
==========================================
+ Coverage   34.52%   34.54%   +0.01%
==========================================
  Files         109      109
  Lines       52604    52612       +8
==========================================
+ Hits        18160    18173      +13
+ Misses      34444    34439       -5


WAILA scanning should fail if wrong network

@TonyGiorgio just scanned signet unified qr from a mainnet wallet and ended up on a lightning send

I believe this is fixed now by #152
https://github.com/MutinyWallet/mutiny-web/pull/152/files#diff-7b36bdac6134c93204d526643a2413646a20fe6753c90c904e56f60cbd093bbeR29
but want to test on mainnet to be sure


部署后无法访问，麻烦帮忙看一下。谢谢。

配置成功
Vmess-ibm-clone(104***226:443)
启动服务(2020-09-11 09:38:01)...
V2Ray 4.27.0 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.14.6 windows/386)
A unified platform for anti-censorship.
2020/09/11 09:38:01 [Info] v2ray.com/core/common/platform/ctlcmd:
v2ctl> Read config:  D:\Program Files\v2ray\config.json
2020/09/11 09:38:01 [Warning] v2ray.com/core: V2Ray 4.27.0 started
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62946 accepted tcp:alive.github.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62952 accepted tcp:i.ytimg.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62953 accepted tcp:yt3.ggpht.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62954 accepted tcp:www.youtube.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62947 accepted tcp:alive.github.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62955 accepted tcp:i.ytimg.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62956 accepted tcp:i.ytimg.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62957 accepted tcp:yt3.ggpht.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62958 accepted tcp:i.ytimg.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62959 accepted tcp:yt3.ggpht.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62942 accepted tcp:<IP_ADDRESS>:80 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62961 accepted tcp:<IP_ADDRESS>:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62962 accepted tcp:[2001:b28:f23f:f005::a]:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62963 accepted tcp:<IP_ADDRESS>:80 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62964 accepted tcp:i.ytimg.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62965 accepted tcp:i.ytimg.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62966 accepted tcp:yt3.ggpht.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62967 accepted tcp:yt3.ggpht.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62969 accepted tcp:yt3.ggpht.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62970 accepted tcp:www.youtube.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62971 accepted tcp:www.youtube.com:443 [proxy]
2020/09/11 09:38:02 tcp:<IP_ADDRESS>:62972 accepted tcp:www.youtube.com:443 [proxy]
2020/09/11 09:38:03 <IP_ADDRESS>:62974 accepted tcp:<IP_ADDRESS>:0 [api]
2020/09/11 09:38:03 tcp:<IP_ADDRESS>:62975 accepted tcp:www.youtube.com:443 [proxy]
2020/09/11 09:38:03 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > websocket: close 1000 (normal)
2020/09/11 09:38:03 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > websocket: close 1000 (normal)
2020/09/11 09:38:04 tcp:<IP_ADDRESS>:62977 accepted tcp:[2001:b28:f23f:f005::a]:443 [proxy]
2020/09/11 09:38:04 tcp:<IP_ADDRESS>:62976 accepted tcp:<IP_ADDRESS>:443 [proxy]
2020/09/11 09:38:04 tcp:<IP_ADDRESS>:62978 accepted tcp:<IP_ADDRESS>:80 [proxy]
2020/09/11 09:38:04 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > websocket: close 1000 (normal)
2020/09/11 09:38:04 tcp:<IP_ADDRESS>:62980 accepted tcp:www.youtube.com:443 [proxy]
2020/09/11 09:38:04 tcp:<IP_ADDRESS>:62981 accepted tcp:yt3.ggpht.com:443 [proxy]
2020/09/11 09:38:04 tcp:<IP_ADDRESS>:62982 accepted tcp:www.youtube.com:443 [proxy]
2020/09/11 09:38:04 tcp:<IP_ADDRESS>:62985 accepted tcp:www.youtube.com:443 [proxy]
2020/09/11 09:38:04 tcp:<IP_ADDRESS>:62983 accepted tcp:www.youtube.com:443 [proxy]
2020/09/11 09:38:04 tcp:<IP_ADDRESS>:62984 accepted tcp:yt3.ggpht.com:443 [proxy]
2020/09/11 09:38:04 tcp:<IP_ADDRESS>:62986 accepted tcp:yt3.ggpht.com:443 [proxy]
2020/09/11 09:38:04 tcp:<IP_ADDRESS>:62988 accepted tcp:i.ytimg.com:443 [proxy]
2020/09/11 09:38:04 tcp:<IP_ADDRESS>:62989 accepted tcp:i.ytimg.com:443 [proxy]
2020/09/11 09:38:04 tcp:<IP_ADDRESS>:62991 accepted tcp:yt3.ggpht.com:443 [proxy]
2020/09/11 09:38:04 tcp:<IP_ADDRESS>:62990 accepted tcp:i.ytimg.com:443 [proxy]
2020/09/11 09:38:04 tcp:<IP_ADDRESS>:62992 accepted tcp:<IP_ADDRESS>:80 [proxy]
2020/09/11 09:38:05 tcp:<IP_ADDRESS>:62993 accepted tcp:www.youtube.com:443 [proxy]
2020/09/11 09:38:05 tcp:<IP_ADDRESS>:62994 accepted tcp:i.ytimg.com:443 [proxy]
2020/09/11 09:38:05 tcp:<IP_ADDRESS>:62995 accepted tcp:yt3.ggpht.com:443 [proxy]
2020/09/11 09:38:05 tcp:<IP_ADDRESS>:62996 accepted tcp:alive.github.com:443 [proxy]
2020/09/11 09:38:05 tcp:<IP_ADDRESS>:62997 accepted tcp:alive.github.com:443 [proxy]
2020/09/11 09:38:05 tcp:<IP_ADDRESS>:62998 accepted tcp:i.ytimg.com:443 [proxy]
2020/09/11 09:38:05 tcp:<IP_ADDRESS>:62999 accepted tcp:i.ytimg.com:443 [proxy]
2020/09/11 09:38:05 tcp:<IP_ADDRESS>:63000 accepted tcp:yt3.ggpht.com:443 [proxy]
2020/09/11 09:38:05 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > websocket: close 1000 (normal)

客户端要更新，协议是V L ESS。