Failed to build pip package for Python 3: PyString_FromStringAndSize not declared

I was building pip package for Python 3.5. bazel reported an error during
bazel build -c opt --config=cuda //tensorflow/tools/pip_package:build_pip_package --verbose_failures

The failing command was:
cd /home/z/.cache/bazel/_bazel_z/4c5a3f7b23103a2fe3f8cd834eaf9376/tensorflow && \
exec env - \
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games \
third_party/gpus/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc \
(lots of flags here)
-c bazel-out/local_linux-py3-opt/bin/tensorflow/python/pywrap_tensorflow.cc \
-o bazel-out/local_linux-py3-opt/bin/tensorflow/python/_objs/_pywrap_tensorflow.so/tensorflow/python/pywrap_tensorflow.pic.o

The error was:
bazel-out/local_linux-py3-opt/bin/tensorflow/python/pywrap_tensorflow.cc: In function 'PyObject* _wrap_TF_PRunSetup(PyObject*, PyObject*)':
bazel-out/local_linux-py3-opt/bin/tensorflow/python/pywrap_tensorflow.cc:4974:66: error: 'PyString_FromStringAndSize' was not declared in this scope
       resultobj = PyString_FromStringAndSize(*arg6, strlen(*arg6));
                                                                  ^

It seemed to be a Python 2/3 compatibility issue, since PyString_FromStringAndSize is no longer provided by Python 3 headers.
pywrap_tensorflow.cc reads like:
  resultobj = SWIG_Py_Void();
  {
    if (!arg5->ok()) {
      RaiseStatusNotOK(*arg5, SWIGTYPE_p_tensorflow__Status);
      SWIG_fail;
    } else {
      resultobj = PyString_FromStringAndSize(*arg6, strlen(*arg6));
      delete *arg6;
    }
  }
  return resultobj;

I'm not sure whether it was caused by tensorflow or my configuration, but I did find some suspicious code in tensorflow/python/client/tf_session.i, that closely resembles the problematic code:
https://github.com/tensorflow/tensorflow/blob/97f585d506cccc57dc98f234f4d5fcd824dd3c03/tensorflow/python/client/tf_session.i#L211

change tf_session.i line 211:
$result = PyString_FromStringAndSize($2, strlen($2));
To:
%#if PY_MAJOR_VERSION < 3
$result = PyString_FromStringAndSize(
%#else
$result = PyUnicode_FromStringAndSize(
%#endif
$2, strlen($2));

The fix proposed by @blueegg worked for me. Thanks.

We fixed this recently in https://github.com/tensorflow/tensorflow/commit/5ff6d34a05b2eb49f7a79a4d0b78ada9a6842b6c


Wrong current co-plotted when highlighting current used for calibr. in ecms_calibration_curve

When co-plotting the current used in the calibration on a plot which has been calibrated to show current density by passing the axis to ecms_calibration_curve, the raw current will be co-plotted. of course, the raw current needs to be used for the calculation, but I think when highlighting in the plot, it would still make sense to highlight using the current density, just for looks of the plot. or do you think that's suggestive of the function actually using the current density and thereforte misleading? @ScottSoren
Edit: if we dont want to allow it to highlight the current density, then I think we need to disallow it/give a warning if the current axis unit is not the same

This may be tricky, as the ecms_calibration_curve method plots that highlight on an axis passed to it. The information about what unit is plotted is not stored in the axis, so I'm not sure how the method could figure it out. Reading the axis label would be fragile, since the user could have changed it. Even implementation of pint in ixdat won't help - it would have to somehow be implemented in matplotlib! The best might just be to specify in the docstring that the axis passed to it should not have the current in [mA].

Ok, I didn't consider that the axis doesn't know what unit is plotted on it.
"The best might just be to specify in the docstring that the axis passed to it should not have the current in [mA]." - I'm not quite sure I understand what you mean by that. Do you mean we should be more specific that it won't work if calibrated data is plotted on the axis?
What about giving a possibility of passing to the method not only what axis to highlight, but also which unit this axis uses? i.e. not rely on it to be done automatically, but give the option to modify it?

acceptable fix for now, but see https://github.com/ixdat/ixdat/issues/130


Order of domain_name_servers and domain_name options matter

I don't know if this is an intended behaviour or a bug, but the order of domain_name and domain_name_servers options for static configuration matters. In fact, domain name should be configured first, otherwise the list of DNS servers is not applied (or maybe gets reset?).
$ dhcpcd --version
dhcpcd 9.4.1
Copyright (c) 2006-2021 Roy Marples
Compiled in features: INET ARP ARPing IPv4LL INET6 DHCPv6 AUTH PRIVSEP

With domain name preceding DNS servers, it works as expected:
$ dhcpcd -d --static ip_address=<IP_ADDRESS>/24  -b -t 0 --static "domain_name=mydomain" --static "domain_name_servers=<IP_ADDRESS> <IP_ADDRESS>" eth0
no such user dhcpcd
dhcpcd-9.4.1 starting
spawned manager process on PID 7406
DUID 00:01:00:01:2b:73:88:e1:02:fe:22:1a:87:00
forked to background, child pid 7406

$ dhcpcd -U -4 eth0
no such user dhcpcd
reason=STATIC
interface=eth0
protocol=dhcp
ip_address=<IP_ADDRESS>
subnet_cidr=24
broadcast_address=<IP_ADDRESS>
network_number=<IP_ADDRESS>
subnet_mask=<IP_ADDRESS>
domain_name=mydomain
domain_name_servers=<IP_ADDRESS> <IP_ADDRESS>

However, if domain_name_servers are specified first, they will be ignored:
$ dhcpcd -d --static ip_address=<IP_ADDRESS>/24  -b -t 0 --static "domain_name_servers=<IP_ADDRESS> <IP_ADDRESS>" --static "domain_name=mydomain" eth0
no such user dhcpcd
dhcpcd-9.4.1 starting
spawned manager process on PID 7297
DUID 00:01:00:01:2b:73:88:e1:02:fe:22:1a:87:00
forked to background, child pid 7297

$ dhcpcd -U -4 eth0
no such user dhcpcd
reason=STATIC
interface=eth0
protocol=dhcp
ip_address=<IP_ADDRESS>
subnet_cidr=24
broadcast_address=<IP_ADDRESS>
network_number=<IP_ADDRESS>
subnet_mask=<IP_ADDRESS>
domain_name=mydomain

Although I haven't tested dhcpcd with a configuration file, it seems that the same issue is also reproducible if config file is used instead of command line arguments, as reported in this comment.

Thank you @rsmarples for fixing this so quickly!


Bump allocate downward

It should be fairly straightforward to adjust the allocator to bump-allocate downward from the end of a block rather than upward from the beginning.  See https://fitzgeraldnick.com/2019/11/01/always-bump-downwards.html for an explanation.
Bump allocation happens inside an available set of Immix lines. The "find-next-line" operation can still look upward for the next set of free lines, but within lines, allocation should bump downward from the end of the lines.
Things to take into account:

word 0 of a block is currently used to point at the block metadata
the code should be updated - stickyimmix/src/bumpblock.rs
the book text should be updated - chapter booksrc/chapter-simple-bump.md

I'm not thrilled with the level and quality of unit testing yet, so consider what new tests can improve coverage and corner cases as part of this.

I'd love this to be a "good first issue" but it does require understanding of Immix and the subject matter in general. It's not such a small issue either due to the need to update the book.

Additionally, as the book chapter in alignment states, objects should be aligned on double-word boundaries. The object header should be aligned on a word boundary. These constraints are not correctly implemented yet and should be as part of this issue.

Additionally number 2: the metadata should be inside the memory block, not a separately allocated data structure. I originally did that for easier type management.


Reopen the camera in web

When reopen the camera we stuck the camera
https://github.com/juliansteenbakker/mobile_scanner/assets/33222592/fd95e396-9f8e-4374-9dcb-4771b654a391

This was already fixed in mobile_scanner 5.0.0-beta.3


Implement better React key-assignment algorithm for controls

Currently, we're just using array indices as keys for our rendered list of control components. But if the contents of our controls list changes on a component update, we should be able to determine which newly-listed controls match those which were previously mounted. This will be particularly important if a control instance is holding its own state, which we would prefer not to lose.

Leaving on 2.0 milestone for now, but the same implementation should be applied in master after #47 is resolved, for the 1.2 release.

Very much a work in progress... just trying to write these thoughts down somewhere:
const newControls = [...nextProps.controls];
const oldControls = [...this.props.controls];
for (const control of newControls) {
  const matchingIndex = oldControls.indexOf(control);
  if (matchingIndex !== -1) {
    const matchingControl = oldControls.splice(matchingIndex, 1)[0];
    // this part is totally magic and we need a data structure for keeping
    // track of new keys/old keys (where multiple rendered instances could
    // share the same class). Obviously we can’t actually attach keys to
    // the class objects.
    control.key = matchingControl.key;
  } else {
    // we also need an algorithm for assigning new keys
    control.key = getNewKeyMagicallySomehow();
  }
}

Boom!
// somewhere
let nextControlKey = 0;
function getNextControlKey () {
  return (nextControlKey++).toString();
}

// in constructor
this.controlKeys = props.controls.map(getNextControlKey);

// in componentWillReceiveProps
const oldControls = [...this.props.controls];
this.controlKeys = nextProps.controls.map(control => {
  const matchingIndex = oldControls.indexOf(control);
  if (matchingIndex !== -1 && oldControls[matchingIndex]) {
    oldControls[matchingIndex] = null;
    return this.controlKeys[matchingIndex];
  }
  return getNextControlKey();
});

Leaving open until included in master for 1.2 release.


When using pytest-xdist with pytest the total duration in test explorer is wrong

When using pytest-xdist for parallel test execution, the total time taken is NOT the same as the sum total of all tests.

@luabud we'll need to prioritize this, hence adding a label of needs decision.

Here's what we do today:

We display a summary for each node in the tree

For folder (nodes) we display the sum total of all child nodes
For file (nodes) we display the sum total of all child nodes

Unfortunately

When running tests in parallel, pytest is responsible for the tests, not us
We have no idea what ran in parallet and what didn'
So, its possible two files ran in parallel, and displaying a total time for a folder node makes no sense, as this information is not available (pytest doesn't deal with test folders, it deals with tests & not even test files)
By the same token we don't know how long a test file took to complete, all we know is how long each individual test in the file took.

Again, displaying the total time taken for all tests in a file is wrong.
Tests can run in parallel, and we don't have the information

Same applies to a test suite...

Suggestion

We display the time taken to run tests ONLY for each test function (not a folder, not a file, & not for a suite)
We can display the total time taken to run the tests at the root folder, ONLY if there is ONE root folder.

This is because we only know how long ALL tests took
If we have tests in two folders at the top level, then we don't know how long each folder took...

This change will have to be made across the board, as we have no idea what tests ran in parallel and what didn't, & we shouldn't try to guess nor assume (unnecessary hacks).

Solution:

Display the time only for the individual test
Do not display summary for suite, file, folder

validated


No callback on Windows

Tried setWindowSleepHandler, but cant get any event. Windows 10

have you tried the example project is it working?


bos can't connect to default 0.14 lnd

bos 11.12.1
lnd 0.14.1
bos can't connect to lnd that uses default rpc and macaroon+cert locations anymore after upgrading to 0.14.1 from 0.13.4
If i use a credentials.json and --node the commands work.
My credentials json with default paths:
{
  "cert_path": "/home/bitcoin/.lnd/tls.cert",
  "macaroon_path": "/home/bitcoin/.lnd/data/chain/bitcoin/mainnet/admin.macaroon",
  "socket": "localhost:10009"
}

It worked without a credentials.json before the upgrade to lnd 0.14+
This is the error from bos peers other commands return similar errors:
err:
  - 503
  - UnexpectedGetPeersError
  -
    err:
      message: 14 UNAVAILABLE: No connection established
      stack:
        - Error: 14 UNAVAILABLE: No connection established
        -     at Object.callErrorFromStatus (/home/bitcoin/.nvm/versions/node/v16.13.0/lib/node_modules/balanceofsatoshis/node_modules/@grpc/grpc-js/build/src/call.js:31:26)
        -     at Object.onReceiveStatus (/home/bitcoin/.nvm/versions/node/v16.13.0/lib/node_modules/balanceofsatoshis/node_modules/@grpc/grpc-js/build/src/client.js:180:52)
        -     at Object.onReceiveStatus (/home/bitcoin/.nvm/versions/node/v16.13.0/lib/node_modules/balanceofsatoshis/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:336:141)
        -     at Object.onReceiveStatus (/home/bitcoin/.nvm/versions/node/v16.13.0/lib/node_modules/balanceofsatoshis/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:299:181)
        -     at /home/bitcoin/.nvm/versions/node/v16.13.0/lib/node_modules/balanceofsatoshis/node_modules/@grpc/grpc-js/build/src/call-stream.js:160:78
        -     at processTicksAndRejections (node:internal/process/task_queues:78:11)

Maybe it has something to do with tor.skip-proxy-for-clearnet-targets ? I use that option with my lnd

it would look in the default locations so probably the issue is there is some custom hostname and that confuses it

Ah, that has improved the situation, bos nodes giving sensible output now, the other command is not though. Here's bos nodes
bos@raspberrypi:~ $ bos nodes --verbose
(node:3430658) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.
(Use `node --trace-deprecation ...` to show where the warning was created)

nodes:
  -
    is_online:  true
    node_name:  the0ther
    public_key: 03590bc434aaba157588dc84XXXXXXXXXX5d7848bc10f6a564ba3248ea68e
  -
    is_online:  true
    node_name:  the0therstore.duckdns.org
    public_key: 03590bc434aaba157588dc84b74XXXXXXXXXXXX5d7848bc10f6a564ba3248ea68e

try using bos --node the0ther chart-fees-earned --days 7


go-mockery: 2.9.2 -> 2.12.2

Description of changes

Package update
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Tests are not passing, it seems that fixtures are not properly discovered :/
Do you have an idea @cideM ?

Sorry for the delay. I'm looking into this right now but I can't promise anything since I just don't have much time to dedicate to this right now :(
At first glance the path that Mockery is using in its tests doesn't exist in the build directory Nix uses.
$ ls /private/tmp/nix-build-go-mockery-2.12.2.drv-0/source/pkg/
compat_test.go  generator.go       mockery.go       outputter_test.go  walker.go
config/         generator_test.go  mockery_test.go  parse.go           walker_test.go
fixtures/       logging/           outputter.go     parse_test.go

Notice there's no
                                open /private/tmp/nix-build-go-mockery-2.12.2.drv-0/source/pkg/github.com/vektra/mockery/v2/pkg/fixtures: no such file or directory

in there.

superseded by later updates.


Y24-061: Research the best way to pass Pool XP tube export messages from Limber to RabbitMQ

Description
An endpoint needs to be available in Sequencescape for Limber to be able to call so that a Pool XP tube will generate an appropriate message in Avro format and publish it to the RabbitMQ exchange which will be consumed by the TOL Lab Share tool.  See the EPIC for more information.  What we want to know is how we are going to create this endpoint in Sequencescape while limiting the changes we make to the system and keeping this away from existing APIs which are already harder to maintain than we'd like.
Who the primary contacts are for this work
Stuart McHattie
Knowledge or Stake holders
Andrew Sparkes
Stephen Inglis
Ben Topping
Thomas Whiteley
Additional context or information
This is part of the EPIC: https://github.com/sanger/sequencescape/issues/3754

We (PSD) had a call today about this.  There are still a lot of unknowns, but the general gist is that we will either add to the v2 endpoint or create something separate.  The message to this API will be super simple only indicating the tube to export.  The endpoint will cascade into creating an AVRO schema compliant message for RabbitMQ which will either be a new system (since this is going to get reused) or will be development of Warren.  Warren is a source of technical debt now that the author is not working with us, so we might look for a way to replace it if it is not easily extensible.  None of this will be done before we have the message AVRO schema format agreed.

Generating Avro encoded messages in Ruby requires a new library to be used.  The official library is badly documented, much like all the other language variants I've seen from Apache.  However I've pieced together the correct combination of objects to encode a message to put on RabbitMQ.  It's worth noting that the official library is only capable of writing binary encoded messages, rather than JSON format messages which ToL-lab-share is capable of decoding.  I did look at other libraries as well which extend this one, but they don't provide any additional functionality that we want and often add complications like only reading schemas from files on disk.  Obviously when we create the Schema object, we will use the JSON string obtained from RedPanda and not from a file.
#!/bin/env ruby

require 'avro'

schema_str = File.read('schema.avsc')
message_obj = JSON.parse(File.read('test_message.json'))

schema = Avro::Schema.parse(schema_str)
stream = StringIO.new
writer = Avro::IO::DatumWriter.new(schema)
encoder = Avro::IO::BinaryEncoder.new(stream)
writer.write(message_obj, encoder)
message = stream.string

The research in how to encode these messages correctly using Ruby and Python is in the GitLab Data Patch Archive repository: https://gitlab.internal.sanger.ac.uk/psd/data-patch-archive/-/tree/main/avro-tests/encoding-decoding?ref_type=heads
It's worth noting that the Ruby library for Avro does not create a parsing form for schemas that is consistent with fastavro which I have confirmed is the correct form.  It misses off the namespace on custom named types, and so the schema.crc_64_avro_fingerprint is useless outside of Ruby implementations.  We will need to extend the functionality of the Ruby Avro library when generating these files so that we can ensure the correct parsing form is generated for hashing.
We will need to adapt lab-share-lib to consume these messages.  We can provide support for both binary forms, either by checking for the presence of the two-byte marker and choosing how to decode the binary, or more likely by trying to parse the binary with the regular binary reader and catching a failure to decode, then switching to the single-object container format shown in the above code.


Form editor for umbraco 8

Is it possible to get a version of this project available for umbraco 8+? Or is there an easy way to make the forms created in umbraco 7.14 with formEditor running on umbraco 8?

Hi @MastuaCR,
There are currently no plans of porting this to V8+ ... and I doubt there's any easy way to make a quick fix that will allow the V7 forms to work on V8.


Add an extra option to inform that a module is a core NodeJS module

This PR adds an extra, optional parameter, into the Options object passed to transform. The option is named isCoreModule, and it is intended to be used later by the re-injection of native modules inside the contexts.
It is required to ensure that modules are never transformed or instrumented, but that they are wrapped and returned as a vm.Script instance.

I will hold off to review this until I understand the direction you are taking with core modules and the PRs on top of this one if you don't mind. I can't wrap my head about this yet.

Codecov Report

Merging #4950 into master will increase coverage by 0.05%.
The diff coverage is 92.3%.

@@            Coverage Diff             @@
##           master    #4950      +/-   ##
==========================================
+ Coverage   60.26%   60.31%   +0.05%
==========================================
  Files         198      198
  Lines        6594     6600       +6
  Branches        3        4       +1
==========================================
+ Hits         3974     3981       +7
+ Misses       2620     2619       -1

Impacted Files
Coverage Δ

packages/jest-runtime/src/script_transformer.js
86.5% <92.3%> (+1.15%)
:arrow_up:

Continue to review full report at Codecov.

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

Maybe I can explain here the simplified idea: I want to replace this require call, with a process.binding('natives')[moduleName] and then evaluate the result via this._environment.runScript.
This will cause native modules to get re-evaluated, thus returning different instances than the ones used by the main Jest process (i.e. outside of the VM context).

This is amazing. This is going to fix so many issues about native objects from different contexts.


Can I delete the Installer VPC?

Is your feature request related to a problem? Please describe.
Can I delete the Installer VPC?
Describe the solution you'd like
I'd like to delete the installer VPC or specifically the 2 nat gateways that run there.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

I do have an active support, so if I should open a case there instead I can.
I had assumed the installer and installer VPC would delete itself after running. The fargate tasks are gone, but the VPC and NAT instances still remain.

Doesn't happen in the latest version. Thx.


Reject on onSnapshot error

Please can you add reject in onSnapshot error in functions "collections" and "documents" to be able to detect for example "permission-denied" errors
Thanks

Thanks for submitting this issue!!
The bind function already returns a promise, you can simply trigger that manually.
  this.$binding("users", firebase.firestore().collection("users"))
  .then((users) => {
    console.log(users) // => __ob__: Observer
  }).catch(error) => {
      console.error(error.message)
  }

Hi,
that only works if the problem is with the docChanges.forEach
source.onSnapshot(doc => {     doc.docChanges.forEach(snapshot => {       ...     }, reject)   }) }
You should add a new reject in onSnapshot
source.onSnapshot(doc => {     doc.docChanges.forEach(snapshot => {       ...     }, reject)   }, reject) }
The same for the documents
source.onSnapshot(doc => {    ...   }, reject)
You can test it trying to access a collection in firestore where you don't have permissions
Regards

Without the extra reject if you try the next code and receive an "Error: Missing or insufficient permissions.":
component       .$binding('tests', firebase.db.collection('tests'))       .then(tests => {         ...       })       .catch(error => {         // Not enter       })
Regards

Fixed!!
Thanks :+1:


chore(poc): add a new workflow for the a11ytester-action action

To be reopened if we want to implement #1180


The command is wrong in readme.md it should be azd env set ALLOWED_ORIGIN https://<your-domain.com>

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

azd version?

run azd version and copy paste here.

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Thanks! Fixing in https://github.com/Azure-Samples/azure-search-openai-demo/pull/723


Update Catch to 2.13.1

Just a regular update, nothing interesting. Will merge once all the tests pass.

Coverage remained the same at 57.18% when pulling 767eba18edf86a97d06234bfcda655091dbbe3d5 on feature/update-catch2 into 9d97282a13dfceaf4bfbc6d920341e3c0cff104f on master.


Gauge should accept integer values instead of double

Hi,
I have noticed that Gauge is accepting and sends double values which are not accepted by the Jroland/StatsdNet service. For it to work with the service, the value should be an integer.

Looks like it was changed to doubles in https://github.com/goncalopereira/statsd-csharp-client/commit/0c317d542505c8fee6257888a7df104924165b77. Do you remember why @goncalopereira?

So the "official" statsd spec says "Most implementations store values internally as a IEEE 754 double precision float, but many implementations and graphing systems only support integer values." Whisper seems to store as float, and statsd seems to support floats, so I think a double is probably a better option here over an int/long. Maybe decimal. Either way I haven't had any more requests so going to close this issue.


[Staff-Commands] Hub

Mods and i assume below do not have access to /checkban player while in the hub

Be [Mod]
connect to /hub
use command `/checkban player'
See error

for /checkban to work and return the proper information
Deathnight7976
Hub
Other commands with such issues include /cmi options chatspy (enable/disable)

Fixed!


Remove or fix overscan references in docs

There are places where overscan is mentionend in documenetation and it needs to be updated

This think this could be closed. Documentation was updated after the merge of #381.

Ok, thanks @Allonck


Slider Component is throwing error while using in React app

Prerequisites

[X] I have read the Contributing Guidelines.
[X] I have not leaked any internal/restricted information like screenshots, videos, code snippets, links etc.

What happened?
Cannot read properties of undefined (reading 'forEach')
TypeError: Cannot read properties of undefined (reading 'forEach')

example
What type of frontend framework are you seeing the problem on?
React
Which version of iX do you use?
v2.2.0
Code to produce this issue.
https://stackblitz.com/run?file=src%2Fslider.tsx

In Siemens IX offical documentation stackbliz example for react having this issue

Duplicated issue #1249. Fix part of next release.


Can't connect accessory to multiple IOS Devices.

Hi I am using the latest version of IOS.
However I am not able to connect my accessory to my iPad. Once it is connected to my iPhone, my iPad can't find the accessory.
Thanks in advance! @KhaosT

Hey there,
I ran into the same issue, when I started with this project myself.
This has to do with the basic architecture of HomeKit by Apple. You only can setup your accessories once on one iOS device/home/account.
Once you configured your accessories on e.g. your iPhone, you have to "share" your home with other users (via Apple ID). If your iPad uses the same Apple ID, try to start over: remove all accessories, remove all homes, reset HomeKit in your Settings/Privacy and check that your iCloud keychain is configured properly.
Hope I could help.

When I invite someone to my Home. The person is not getting an email @futuretec

@Techchunky I don't think you'll get an email.
At first you got to use a valid iCloud/Apple ID email address. Then a banner should appear on the invitee's device. If it doesn't check Settings -> HomeKit if they can accept the invite.

I second that, no email, just a notification. Using the HMCatalog app in Apples examples, and works flawlessly with the latest HAP-NodeJS.

Hmm, not getting a notification.. @AdySan @futuretec

Ah it worked!! Thanks

It worked Thanks to @AdySan @futuretec

It worked Thanks to @AdySan @futuretec


[CHANGE ME] Re-generated to pick up changes from synthtool.

This PR was generated using Autosynth. :rainbow:
Synth log will be available here:
https://source.cloud.google.com/results/invocations/70bf6d99-f693-457e-860b-85ee7d8833eb/targets

[ ] To automatically regenerate this PR, check this box. (May take up to 24 hours.)

Source-Link: https://github.com/googleapis/synthtool/commit/5b5bf6d519b2d658d9f2e483d9f6f3d0ba8ee6bc
PiperOrigin-RevId: 365856330
Source-Link: https://github.com/googleapis/googleapis/commit/ef705a6d9fd6dcd8f0b13e012cb284332734785b

Superseded by #87


porting protocol changes btween 54455 and 54459

PR checklist:

Did you run ClangFormat ?
Did you separate headers to a different section in existing community code base ?
Did you surround proton: starts/ends for new code in existing community code base ?

Please write user-readable short description of the changes:
The commit https://github.com/timeplus-io/proton/commit/b236bd423795f7e1b0b26ab346ae32d1f71f6cb8#diff-853b8e1a887784623fa5fe94e831ef320fa480ecc074804337ed629b9203f739R58 updated the protocol from 54455 to 54459. However, it skipped the changes between these two revisions. And this caused problems for establishing connections to a CH server. This PR cherry-picked all the changes between those two revisions, and neccessariy dependencies.
Cherry-picked changes include:
Author: Yakov Olkhovskiy<EMAIL_ADDRESS>Date:   Wed Aug 10 00:12:44 2022 -0400

    Merge pull request #39874 from ClickHouse/fix-quota-key

    Fix quota_key

Author: Vitaly Baranov<EMAIL_ADDRESS>Date:   Tue Jun 7 10:17:39 2022 +0200

    Merge pull request #37303 from ClickHouse/fix_trash

    Try to fix some trash

Author: Vitaly Baranov<EMAIL_ADDRESS>Date:   Thu May 19 09:20:52 2022 +0200

    Merge pull request #36941 from nvartolomei/nv/show-grants-current-roles

    Allow a user to inspect grants from granted roles

Author: Maksim Kita<EMAIL_ADDRESS>Date:   Wed Feb 2 22:51:51 2022 +0100

    Merge pull request #34225 from vitlibar/fix-checking-grants-for-show-grants

    Fix checking grants for SHOW GRANTS

Author: Kruglov Pavel<EMAIL_ADDRESS>Date:   Thu Jul 21 11:37:20 2022 +0200

    Merge pull request #39413 from vitlibar/fix-interactive-client-with-older-server

    Fix interactive client with older server

Author: Kseniia Sumarokova<EMAIL_ADDRESS>Date:   Fri Apr 22 11:52:40 2022 +0200

    Merge pull request #36481 from kssenii/fix-client-exception

    Fix possible exception with unknown packet from server in client

Author: Kseniia Sumarokova<EMAIL_ADDRESS>Date:   Mon Jun 20 12:16:29 2022 +0200

    Merge pull request #37391 from azat/insert-profile-events-fix

    Send profile events for INSERT queries (previously only SELECT was supported)

Author: Alexey Milovidov<EMAIL_ADDRESS>Date:   Fri Mar 4 23:32:38 2022 +0100

    Remove useless define

(Jove Github Bot) added it to the current sprint.

(Jove Github Bot) moved this ticket out of the GitHub project(up to 1200 tickets for one project).


Cydia clear

After a successful jailbreak, device resprings( for a unsuslly long time based on other unc0ver jb) when finished, Cydia is in my home screen but when opened it just shows a clear screen before crashing - others seem to be having the same issue. Have tried restoring rootfs.
Pressing reinstall cydia just freezes device and reboots.
Screenshots
If applicable, add screenshots to help explain your problem.

Device (please complete the following information):

iOS Version: iOS 13.2.3
iOS Device: iPhone 11
unc0ver Version: 4.0.0

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[x ] this issue is present after a rootfs restore
[ X] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.

am having the same problem here

how can it be fixed

same exact issue here...

Same here!

What’s your guys iOS versions

13.2.3

You guys can go into unc0ver settings uncheck everything and check off reinstall Cydia then click jailbreak

13.2.3

I know yours

Reinstalling cydia causes our phones to freeze then reboot

I could be your iOS version pwn said people with 13, 13.1, 13.2, and 13.3 will have the least problems pwn probably needs to update the jailbreak

13.2 on XS Max for me

13.1 on iPhone XR here

Can confirm issue still exists on v4.0.1 - iOS 13.1 on iPhone XR

Same issue in version 4.0.1
The last answer of pwn gave me some hope for a better release soon...

version 4.0.2 resolved my issue ! Thanks 😊

Still facing the same issue after numerous tries on iPhone XR iOS 13.1 v4.0.2 although it takes more tries to even get a successful jailbreak, most often facing #1696

4.0.2 has resolved my issue.


compdb fails when using 'arguments' instead of 'command' in compile database

When using a tool such as bear (https://github.com/rizsotto/Bear) to build the compilation database for a Makefile based project, the generated compilation database uses the 'arguments' key instead of the 'command' key.
To reproduce:
git clone https://github.com/mbcrawfo/GenericMakefile.git
cd GenericMakefile/cpp
bear make
compdb -p . list

Result:
[
]
Traceback (most recent call last):
  File "/home/rich/bin/compdb", line 9, in <module>
    load_entry_point('compdb==0.1.1', 'console_scripts', 'compdb')()
  File "/home/rich/.local/lib/python2.7/site-packages/compdb-0.1.1-py2.7.egg/compdb/cli.py", line 559, in main
    command.execute()
  File "/home/rich/.local/lib/python2.7/site-packages/compdb-0.1.1-py2.7.egg/compdb/cli.py", line 239, in execute
    for compile_command in compile_commands:
  File "/home/rich/.local/lib/python2.7/site-packages/compdb-0.1.1-py2.7.egg/compdb/core.py", line 50, in <genexpr>
    for db in databases))
  File "/home/rich/.local/lib/python2.7/site-packages/compdb-0.1.1-py2.7.egg/compdb/db/json.py", line 38, in get_all_compile_commands
    return map(self._dict_to_compile_command, self._data)
  File "/home/rich/.local/lib/python2.7/site-packages/compdb-0.1.1-py2.7.egg/compdb/db/json.py", line 43, in _dict_to_compile_command
    shlex.split(d['command']))
KeyError: u'command'

Things that use libclang, such as YCM seem fine with both cmake and bear derived compilation databases, so it would be great if compdb supported both.
This was using compdb 0.1.1

Indeed, it's on my todo list, thanks for reporting.

Bear compatibility should be fixed by 53ae9eeee5db59893788f395de0ebe79112fbfb4.
Thanks for reporting the issue.

Is there way to generate same output scheme like in bear?
For instance:
{
"arguments": [
"c++",
"-c",
"TestMain.hpp"
],
"directory": "/home/user/test",
"file": "TestMain.hpp"
}
Newer clang versions do not support scheme with "command" ;/

It's on the TODO list to print the database in various format.
But it would be better to create a new issue for this.
However, I don't think the reason for this is correct.
The Clang parser should support both arguments and command:

command: The compile command executed. After JSON unescaping, this must be a valid command to rerun the exact compilation step for the translation unit in the environment the build system uses. Parameters use shell quoting and shell escaping of quotes, with ‘"’ and ‘\’ being the only special characters. Shell expansion is not supported.
arguments: The compile command executed as list of strings. Either arguments or command is required.

-- https://clang.llvm.org/docs/JSONCompilationDatabase.html

Okej I will create new issue.
When I tried to use rtags with older compile_command.json scheme that error is appeared:
LIBCLANG TOOLING ERROR: json-compilation-database: Expected array.


usb: disable previously enabled endpoint before re-enabling

When switching between alternate settings of an interface, it is currently possible to call set_endpoint() multiple times on an endpoint without first calling reset_endpoint(). For these situations, it is beneficial to track endpoints for which set_endpoint() has previously been called, and then reset them to properly terminate any transfers, and to return the HAL to the correct state

@jfischer-no

We are working on the new USB support, device part should come into the tree in the next weeks. I would not like to change anything in this "legacy" code that is not bug-fix. What bug in the tree does it fix?

Understood - if the underlying issue is fixed by the refactor, then I can close this PR.
My RT685 USB device application uses the usb_transfer() USB API to communicate with the USB host. After initialization is complete, a read transaction is queued to deal with any OUT traffic from the USB host. If the host decides to change to a different alternate setting, this pending transaction must be canceled. The current implementation of usb_transfer() does not appear to do enough to put the HAL in a state where subsequent read transactions can succeed. The only way I could make things work on my RT685 was to call reset_endpoint() in usb_device.c, then follow it with a set_endpoint() if that same endpoint had been enabled before.

@jfischer-no

We are working on the new USB support, device part should come into the tree in the next weeks. I would not like to change anything in this "legacy" code that is not bug-fix. What bug in the tree does it fix?

Understood - if the underlying issue is fixed by the refactor, then I can close this PR.

It is not a refactor, it is complete new implementation. Please continue on this PR.

My RT685 USB device application uses the usb_transfer() USB API to communicate with the USB host. After initialization is complete, a read transaction is queued to deal with any OUT traffic from the USB host. If the host decides to change to a different alternate setting, this pending transaction must be canceled. The current implementation of usb_transfer() does not appear to do enough to put the HAL in a state where subsequent read transactions can succeed. The only way I could make things work on my RT685 was to call reset_endpoint() in usb_device.c, then follow it with a set_endpoint() if that same endpoint had been enabled before.

@jfischer-no

It is not a refactor, it is complete new implementation. Please continue on this PR.

I will get back to my PRs shortly - I have been busy work other work...

Keeping track of enabled endpoints is not only needed for switching between alternate settings, but also for usb_disable(). That is, the usb_disable() should disable all endpoints that were enabled. This PR is really a part of bug fix for #52339. Disabling the endpoints alone won't fully fix the problem on nrfx, but is really necessary for correct solution. I'll base my fix to #52339 on top of this PR.

@desowin

Keeping track of enabled endpoints is not only needed for switching between alternate settings, but also for usb_disable(). That is, the usb_disable() should disable all endpoints that were enabled. This PR is really a part of bug fix for #52339. Disabling the endpoints alone won't fully fix the problem on nrfx, but is really necessary for correct solution. I'll base my fix to #52339 on top of this PR.

I have addressed the feedback - thanks for your patience...


Availability Zones with Low Priority VMSS

Document says A low-priority scale set is deployed in a single fault domain. If I place a VMSS into 3 different availability zones in a region, wouldn't that imply multiple different fault domains?

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

ID: a1bd5076-fe52-cfca-4173-dec861167812
Version Independent ID: 0122fff1-79e0-446c-00a4-85248a21b6dc
Content: Create an Azure scale set that uses low-priority VMs (Preview)
Content Source: articles/virtual-machine-scale-sets/virtual-machine-scale-sets-use-low-priority.md
Service: virtual-machine-scale-sets
GitHub Login: @mmccrory
Microsoft Alias: memccror

@sozercan Thanks for the feedback! We are currently investigating and will update you shortly.

@sozercan It seems it is possible...

@mmccrory can you confirm on this?

Yep, it's possible. My question is, wouldn't that imply multiple fault domains?

@sozercan I am more interested in if the platform is honoring the zones even though we have the low priority tag. If it in fact is, then yes it would imply multiple fault domains.

@sozercan I will assign this to the author to take a look and consider updating the doc.
@mmccrory please take a look.

Reached out to PM owners and will update the docs as necessary.
#in-progress

Hi there. Is there a way to specify evictionPolicy also on Azure CLI? I couldnt find that Parameter here: https://docs.microsoft.com/en-us/cli/azure/vmss?view=azure-cli-latest#az-vmss-create.
Or is it at least possible to update the VMSS via Azure CLI afterwards to set virtualMachineProfile.evitionPolicy via az vmss update?

During preview, the eviction policy can currently be set with the portal or templates. @mmccrory has some updates scheduled to publish on Monday, however the ability to adjust the eviction policy with the Azure CLI 2.0 is not present. For GA, all tooling should support the eviction policy being set.

Thank you for taking the time to share your product and documentation feedback with us. Your input is valued because it helps us create the right documentation for our customers. Due to the volume of issues in our queue, we are closing open issues older than 90 days. We hope to continue hearing from you. Thank you.


Create ldcyzy.txt

@kawa11 Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Invalid operation when adding service principal to AD group

Describe the bug
Attempting to add a service principal to an active directory group results in the following error:
An invalid operation was included in the following modified references: 'members'.

To Reproduce

Create an AD security group, get the object ID as GROUP_ID
Create a service principal, get the object ID as SP_ID
az ad group add member --group $GROUP_ID --member-id $SP_ID

Expected behavior
Service principal should be added to AD group.
Environment summary

Install method: pip
CLI version: 2.0.47
OS: CentOS 7
Shell: zsh
Python version: 3.6

Are you sure you used the correct SP_ID?
Should be the objectId that is returned by az ad sp list - note this is different to the object ID that you see in the portal!

Oh, I did not realize those were different things. I used the object ID from az ad sp list and that worked just fine. Thanks!
Although it is fairly confusing that both the CLI and the portal have something called an Object ID even though they're different. It would be helpful to include a note in the docs to clarify that... would it make sense to open an issue on this page?

i too experienced this issue  where SP object id showed in the console is not adding into group.
i got object id using az ad sp show --id <application_id> and then added in group .


[Refactor] Refactor to()

@tcbegley I wanted to refactor to() to use apply but it breaks. Can you have a look? Not 100% sure those changes make sense anyway...

@tcbegley I wanted to refactor to() to use apply but it breaks. Can you have a look? Not 100% sure those changes make sense anyway...

My mistake, the failing tests aren't really failing (except for lint)


How to reduce the font size of the calender dates?

It is not possible right now. I will update and release a new build with this feature included sometime soon!

How to reduce the font size?
did you add a method for that?
if yes then please add in "Readme"
Thank you.

Sure. Stay tuned for the next release, today.

Please check release 1.6.0
dependencies {
    implementation 'com.github.tizisdeepan:eventscalendar:1.6.0'
}

I have updated the README.
Happy Coding!

Please check release 1.6.1
dependencies {
    implementation 'com.github.tizisdeepan:eventscalendar:1.6.1'
}

I have updated the README.
Happy Coding!

Thank you.


Removed entity-test-lib as it now moved to tc-passthrough-testing

-also removed JUnit references from poms
This module is being moved to https://github.com/Terracotta-OSS/tc-passthrough-testing

(self-merging since this was discussed with @myronkscott earlier, today)


logs/tailers/journald: fix initial seek

What does this PR do?

When journald log start_position is set to forceEnd, all old logs are uploaded.
This commit fixes usage of sdjounal library to make start_position setting works.
Motivation

See #20416

Additional Notes

none
Possible Drawbacks / Trade-offs

none
Describe how to test/QA your changes

Set journald log start_position config to forceEnd
Start datadog-agent
Check uploaded logs doesn't contain lines before the agent start time

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

@gh123man addressed the suggestion from @maycmlee

Hi @at-wat, can you merge main into your branch please? There was a problem with our CI that is fixed now. I just need to get the CI passing before we merge this.
Thanks

@gh123man merged main into my branch


Is there a way to get the last fetched list (loaded with AJAX)

Hello, I want to customise some actions with this plugin, and for that it'd be very helpful to be able to retrieve the list of elements fetched by AJAX, there is already a way to fetch 1 element (by index), but the full list is private and there is no public method for that.
For example, beside this:
		this.getItemData = function(index) {

			if (elementsList.length < index || elementsList[index] === undefined) {
				return -1;
			} else {
				return elementsList[index];
			}
		};

We could have another method to retrieve the full list, like this:
		this.getItems = function() {
			return elementsList;
		};

Is that possible? It is very simple, I could create a pull request if you need it.
Thank you!

Hey,
I think you have a good idea. Please make a pull request with your code.
Thanks for help.

@pawelczak hello and thank you, this is basically what needs to be implemented, right?
        this.getItems = function() {
            return elementsList;
        };

When you retrieve remote data, is the elementsList private variable updated?

@pawelczak I found another "issue" (I don't know if you'd consider it an issue) when you type the exact same value shown in the autocomplete suggestions and you click outside the input field, the selected callback is not called, that's one of the reasons why I'd like to be able to retrieve the last fetched list, to compare it manually to see if the user typed one of the values.

When you retrieve remote data, is the elementsList private variable updated?

Yes.

This is basically what needs to be implemented, right?

Nope :) you also need to add method to jQuery $.fn. . Are you familiar with Grunt, QUnit and writing unit tests?
For the second issue, I thinks that is the correct behavior, but I will be grateful if you create new issue for this case, so I can put more thought into it.

This works fine, I tested it manually, I know about Unit tests, but I'd still need to learn to install Grunt, etc. to be able to make a proper Pull request
		this.getItems = function () {
			return elementsList;
		}

$.fn.getItems = function () {
	var inputId = $(this).attr("id");

	if (inputId !== undefined) {
		return EasyAutocomplete.easyAutocompleteHandles[inputId].getItems();
	}

	return [];
}

Well, for now, I created a simple PR just to add the function #169 in case you are around and can take a look, in the meantime I'll see if I can install Grunt to run the tests etc. :)

@pawelczak ok I was able to build the files with grunt and I added a test, can you please check this out?

Thanks for help! I've added your changes to master branch.

@pawelczak thank you for merging the PR, I created the other issue: https://github.com/pawelczak/EasyAutocomplete/issues/170
This PR would be harder to implement, though.

@sileence I have a favor, can you write your opinion on issue #153


[Addition]: Cluster back online in Palm Harbor

Hotspot b58 Addresses
13X7sEQ172kzqs5mRaq5fH2REXsaG922hRVv8ZGQcXMYBZvDnM2
112DkoELA6gnkLrVH5Esf1TNGbWuvBU3EeYR1mfVyPPHAfTfo5fm
11Q4KxZJqYpgekdPr66AGC2CaG4hwYNJLQ5Tb8uxvkas58EEYJE
11xpCeQxjmksLRj1yYGzM97BFzdgtPwd9aZ8bp3nw1a5xoVeyzv
11265QRQRUtrEKpp3DNH2vwXe38wHPbRkmDuZUxQKAXXnqwx4jz6
112GSuQykn8k9zq12SFTDvvLaq22x8fMhTSvhnos7J6Qm6MCW5x7
11gpTLLUVDvNkmZv4ajVj3FZBDA3steKhN9SPeGrhPK8NYh1P3w
11fEwSDtr2wfbLiR6UgkSfwVygr6kh3iydRXWu291gXQp3rtdyb
112deXiKbpBjtLQauz2xStre32fPPR1bx5JjH5UWFVQtRxTZbrZD
11EwQFe3FquMEDTKQF1KxLyuMKyJnFEs9MpTeZoEGfLxrb1Dq2H
11fbNPRPZYAKDV7DkkV8gBkjJzyxcQ7J8UjK3aA6UB3vTmabLoq
112idQFb9TU7AtShsFcZKVJ24H2XNjPwD4xdgKQm5hAVG5YCK8bE
117A2YH15VCeDQpo1SmDpSrRRtZrF6gxBEjCan9FyWetVAE9jyL
112eDQqo1JUYVy7zZjhApQ8q7peykoCTxf5E95fKTkJj3CF4uVKi
112EQajE9FJve3vjHDmThDoweXyoRatVLpzz2JaBjNDEEe6pkVcq
11XeTfv1KZg4zY36T2moFmcHFjwxAXmsExXHWq6Y8EqJtAMGk2E
112fZ4SnaoVPYHn5saxnNRRDhf54oN9pdsfXjNehQoXbFTuqCnzg
112GWZcdURquWh2BQ8UU3SAXXku8GqJQZbUe8zmh3VzuCmv7nV95
1122KH3w5JKS4DV2vZFpTTLu78bMu4DJwt9AEAxxcRDESuTeboTf
Discord Handle
EDWARDUP#0274
Reason(s)
Reason(s)
All Pisces miners that are banned yet earning a significant amount of HNT when they should not be allowed to.

We have taken into account this addition request in the next iteration of the denylist. Some or all of the Hotspots listed may be added to the denylist. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.


Undefined array key 1 related to PageRoutesService

i am getting this error when trying to clear config, route etc. i don't know how to solve it. Anyone got any ideas?

at vendor\z3d0x\filament-fabricator\src\Services\PageRoutesService.php:87
   83▕     public function removeUrlsOf(Page $page): void
   84▕     {
   85▕         // First remove the entries from the (ID -> URI) mapping
   86▕         $idToUrlsMapping = $this->getIdToUrisMapping();
➜  87▕         $urls = $idToUrlsMapping[$page->id];
   88▕         $idToUrlsMapping[$page->id] = null;
   89▕         unset($idToUrlsMapping[$page->id]);
   90▕         $this->replaceIdToUriMapping($idToUrlsMapping);
   91▕

1   vendor\z3d0x\filament-fabricator\src\Services\PageRoutesService.php:87
    Illuminate\Foundation\Bootstrap\HandleExceptions::Illuminate\Foundation\Bootstrap\{closure}("Undefined array key 1", "C:\xampp\htdocs\nextxlfabricator\vendor\z3d0x\filament-fabricator\src\Services\PageRoutesService.php")

2   vendor\z3d0x\filament-fabricator\src\Commands\ClearRoutesCacheCommand.php:47
    Z3d0X\FilamentFabricator\Services\PageRoutesService::removeUrlsOf(Object(Z3d0X\FilamentFabricator\Models\Page))```

I did composer update. After this I started getting this error after config:clear or route:clear. And the fabricator pages were giving a 404.

Could you please provide the following details so I can debug this more easily without resorting to a hacky fix?

The values in your project's config/filament-fabricator.php file
The result of executing the following code via php artisan tinker in your project:

Cache::get('filament-fabricator::PageRoutesService::id-to-uri')

this is config/filament-fabricator.php

// config for Z3d0X/FilamentFabricator
return [
    'routing' => [
        'enabled' => true,
        'prefix' => null, //    /pages
    ],

    'layouts' => [
        'namespace' => 'App\\Filament\\Fabricator\\Layouts',
        'path' => app_path('Filament/Fabricator/Layouts'),
        'register' => [
            //
        ],
    ],

    'page-blocks' => [
        'namespace' => 'App\\Filament\\Fabricator\\PageBlocks',
        'path' => app_path('Filament/Fabricator/PageBlocks'),
        'register' => [
            //
        ],
    ],

    'middleware' => [
        \Illuminate\Cookie\Middleware\EncryptCookies::class,
        \Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse::class,
        \Illuminate\Session\Middleware\StartSession::class,
        // \Illuminate\Session\Middleware\AuthenticateSession::class,
        \Illuminate\View\Middleware\ShareErrorsFromSession::class,
        \Illuminate\Foundation\Http\Middleware\VerifyCsrfToken::class,
        \Illuminate\Routing\Middleware\SubstituteBindings::class,
    ],

    'page-model' => \Z3d0X\FilamentFabricator\Models\Page::class,

    'page-resource' => \Z3d0X\FilamentFabricator\Resources\PageResource::class,

    'enable-view-page' => false,

    /*
     * This is the name of the table that will be created by the migration and
     * used by the above page-model shipped with this package.
     */
    'table_name' => 'pages',
];

Could you please provide the following details so I can debug this more easily without resorting to a hacky fix?

The values in your project's config/filament-fabricator.php file
The result of executing the following code via php artisan tinker in your project:

// Each ">" indicates a new line prompt
/*>*/ Cache::get('filament-fabricator::PageRoutesService::id-to-uri')
/*>*/ Page::pluck('id')->toArray()

Psy Shell v0.12.7 (PHP 8.2.12 — cli) by Justin Hileman
> Cache::get('filament-fabricator::PageRoutesService::id-to-uri')
= []

> Page::pluck('id')->toArray()
[!] Aliasing 'Page' to 'App\Livewire\Pages\Page' for this Tinker session.

   BadMethodCallException  Method App\Livewire\Pages\Page::pluck does not exist.

> Page::pluck('id')->toArray()

   BadMethodCallException  Method App\Livewire\Pages\Page::pluck does not exist.

>```

u can send me a message

My apologies, you might need to use the Fully Qualified Name of your Page model class instead of just Page (to disambiguate)

My apologies, you might need to use the Fully Qualified Name of your Page model class instead of just Page (to disambiguate)

Can we send me a message on<PHONE_NUMBER>295?

= [
    6 => [
      "/",
    ],
  ]

> \Z3d0X\FilamentFabricator\Models\Page::pluck('id')->toArray()
= [
    6,
  ]```

before i deleted the table cache to solve the issue temporarily


[Refactoring] some opportunities to use diamond operator

A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide - https://zeppelin.apache.org/contribution/contributions.html
[Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring]

[x] - Task

Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/

Put link here, and add [ZEPPELIN-Jira number] in PR title, eg. [ZEPPELIN-533]

Outline the steps to test the PR here.

Does the licenses files need update?
Is there breaking changes for older versions?
Does this needs documentation?

already signed with travis

@desmorto  thanks for the contribution.

Could you create a JIRA ticket?
files under /thrift are auto-generated, so we can't modify.
You need to the forked repository for Zeppelin. The name must be zeppelin. Please read http://zeppelin.apache.org/contribution/contributions.html#continuous-integration

i added the zeppelin to my travis

@desmorto Then could you close and reopen this PR to retrigger jenkins again?
https://builds.apache.org/job/zeppelin-pull-request/2363/console

i will try it

i really don't understand whats is going on
+ python ./travis_check.py desmorto 75791b8656e38f8b361ed02fb9e4f29e9c086298
[2017-07-19 19:17:25] Author: desmorto, commit: 75791b8656e38f8b361ed02fb9e4f29e9c086298
[2017-07-19 19:17:25] --------------------------------
[2017-07-19 19:17:30] Get build status ...
[2017-07-19 19:17:30] Can't find build for commit 75791b8656e38f8b361ed02fb9e4f29e9c086298 from desmorto
+ RET_CODE=2
+ '[' 2 -eq 2 ']'
+ set +x
-----------------------------------------------------
Looks like travis-ci is not configured for your fork.
Please setup by swich on 'zeppelin' repository at https://travis-ci.org/profile and travis-ci.
And then make sure 'Build branch updates' option is enabled in the settings https://travis-ci.org/desmorto/zeppelin/settings.

If you set already travis CI for your fork, could you provide the link? i can help u.


Added Preprocessing Script for Wazuh API and Modified Wazuh Parser

:warning: Note on feature completeness :warning:
We are narrowing the scope of acceptable enhancements to DefectDojo in preparation for v3. Learn more here:
https://github.com/DefectDojo/django-DefectDojo/blob/master/readme-docs/CONTRIBUTING.md
Description
This PR introduces the wazuh-vulns-extractor.py script, designed to enhance vulnerability reporting from Wazuh. This script ensures precise targeting by intersecting two specific agent groups and appends an 'agent_ip' field for every vulnerability. The updated parser.py utilizes this data, enabling DefectDojo to create endpoints and effectively correlate each vulnerability to a specific agent, streamlining traceability and accountability.
Test results

The changes have been locally tested with sample Wazuh v4.5.2 (latest) vulnerability reports.
The modifications do not disrupt the overall functionality of the parser.

Checklist

[x] Make sure to rebase your PR against the very latest dev.
[x] Features/Changes are submitted against the dev.
[x] Bugfixes are submitted against the bugfix branch.
[x] The PR name is meaningful and relevant.
[x] The code is flake8 compliant.
[x] The code is python 3.11 compliant.
[x] Proper documentation has been included.
[x] Model changes include the necessary migrations.
[x] Added applicable tests to the unit tests.
[x] Proper labels have been added.

Extra information
Moderators: Kindly add the labels:

Import Scans (for updated scanner/importer)
enhancement
feature

Contributors: Git Tips
Rebase on dev branch
If the dev branch has changed since you started working on it, please rebase your work after the current dev.
On your working branch mybranch:
git rebase dev mybranch

In case of conflict:
 git mergetool
 git rebase --continue

When everything's fine on your local branch, force push to your myOrigin remote:
git push myOrigin --force-with-lease

To cancel everything:
git rebase --abort

Squashing commits
git rebase -i origin/dev

Replace pick by fixup on the commits you want squashed out
Replace pick by reword on the first commit if you want to change the commit message
Save the file and quit your editor

Force push to your myOrigin remote:
git push myOrigin --force-with-lease

@vd0n any thoughts about adding  "verified=True" to the Finding? That way, the findings would be listed in the endpoint view as well. Currently an endpoint can have dozens of findings but if you look up the endpoints, it seems they don't have any.
find = Finding(                             title=title,                             test=test,                             description=description,                             severity=severity,                             mitigation="mitigation",                             references=references,                             static_finding=True,                             component_name=package_name,                             component_version=package_version,                             verified=True                         )

@vd0n any thoughts about adding verified=Trueto the Finding (starting line 66)? That way, the findings would be listed in the endpoint view as well. Currently an endpoint can have dozens of findings but if you look up the endpoints, it seems they don't have any.

This should remain optional. Anyone can set verified=True if they upload the findings through the API or select it from the GUI, using the dropdown, and choose True.

Parsers, where DefectDojo approaches some tool's API, are implemented differently. They use models like Tool Configuration and API Scan Configuration.
Please find inspiration in parsers starting with api_ like api_blackduck, api_cobalt, api_sonarqube and others.
https://documentation.defectdojo.com/integrations/parsers/api/

As API importer caused some issues in the past and are also not wished until v3 I guess this way is a good approach to go. It should be implemented as API importer in the future (v3 ongoing) but not for now.

While this is a interesting PR, we can't accept API integrations while we're working on the v3 updates - details in this GH discussion: https://github.com/DefectDojo/django-DefectDojo/discussions/8974
Additionally, API integrations are very hard to test with GH actions unless we run instances of all the APIs we integration with (or have accounts with commercial vendors).
Since you can obviously write code, until we get the product parent/child thing figured out and rev to version 3, this would be best implemented as an external service and called via a cron job or similar.
Thanks for the work but the timing just isn't right.


401 unauthorized error after multiple requests

Hello,

I see 401 Unauthorized status code error after multiple requests (3 in my case).
How do I avoid this error to make unlimited requests? Is there a way I can delay the requests by limiting few requests/minute?

exact error message:
message: '\n\n<TITLE>Unauthorized</TITLE>\n\n\n
Unauthorized
\n
Error 401
\n\n\n',   name: 'RequestError',   statusCode: 401,   headers:    { 'content-type': 'text/html; charset=UTF-8',      'www-authenticate': 'GoogleLogin realm="https://accounts.google.com/ClientLogin", service="androidmarket"',      date: 'Mon, 19 Mar 2018 01:07:35 GMT',      expires: 'Mon, 19 Mar 2018 01:07:35 GMT',      'cache-control': 'private, max-age=0',      'x-content-type-options': 'nosniff',      'x-frame-options': 'SAMEORIGIN',      'x-xss-protection': '1; mode=block',      server: 'GSE',      'alt-svc': 'hq=":443"; ma=2592000; quic=51303431; quic=51303339; quic=51303335,quic=":443"; ma=2592000; v="41,39,35"',      'accept-ranges': 'none',      vary: 'Accept-Encoding',      connection: 'close' } }
EDIT: By the way i am calling api.details and download and in my case i am making another request only after the APK file download & upload is completed 100% which will take approx. 4-5 min. Isn't 5min good amount of time for another request to the api?

Is the pkg param case sensitive for api.details?

Thanks

Probably, the easiest way to avoid 401 is to reinitialize api,  because authorization token invalidates quickly (~2-3 min)

sorry for the late response, but reinitialize api worked.
Thanks @yarafan


"useUTC: false" needs to apply to date, time, datetime2 data types

The "useUTC" parameter only applies to fields with a data type of datetime or smalldatetime.  It does not seem to apply for the data types of date, time, or datetime2.  (It also doesn't apply to datetimeoffset, but this particular data type is supposed to supply the timezone anyway.)
My workaround is to use a SQL query to convert my date and my time fields to datetime fields, but I have several of those across my customers' tables.  Can we make the configuration setting "useUTC: false" apply to date, time, and datetime2 data types to return local dates and times instead of UTC dates and times?

Fixed in upcoming release.


cmd/vet: false positive on +build comment if within a string

go version go1.10 linux/amd64
When running go vet on the following code, it complains that the +build comment is in the wrong place:
package main

const prog = `
// +build foo
package main

func main() {}
`

It's tricky and maybe hard to fix but consider it.
The issue is that vet is looking for things in the wrong places, so it can't use the parser,  yet without parsing the code it's easy to mislead the scanner.

Thanks, Rob.

This was reported earlier here: https://github.com/golang/go/issues/13533

Duplicate of #13533.
That one was closed as too hard to fix for the payoff, which is fair. Closing.


Highlight top N work times

Using a user-entered threshold, highlight the top N long-duration items.

Highlighting the top three constraints.


Expose payer address for Hotspot add_gateway transaction

to enable the app and explorer to display the manufacturer, expose the payer address for every Hotspot. App and Explorer can figure out from there, the manufacturer name.

Fixed by https://github.com/helium/blockchain-http/pull/291


Add derivatives plugin compatibility

Hi, hope everything is well down under. :smile:
This is a work in progress, compatibility with the new derivatives plugin (which replaces versions) works, instead of version in the options you have to specify derivative. But, I haven't tested back compatibility with the versions plugin much. Will try to set up a project with an older shrine version (2.x) and the versions plugin and test it out.
image: Field::Shrine.with_options(
  derivative: :medium
)

Looking forward to this getting merged!

@janosrusiczki is it ready for review or merge?

No, haven't yet had time to test versions compatibility. Will try during
this weekend.
On Fri, May 8, 2020 at 4:37 AM KenZ<EMAIL_ADDRESS>wrote:

@janosrusiczki https://github.com/janosrusiczki is it ready for review
or merge?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/catsky/administrate-field-shrine/pull/6#issuecomment-625581323,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABOIHEE3W2BQMCIBP7XSELRQNO6BANCNFSM4MREOFLA
.

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

Binance
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

3. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share on Twitter

Winners: @AndryYu, @Junne, @backupManager, @471448446, @uitk23009, @JackeyLove1, @ShengHsiang, @yedy99, @ijiroterunao, @kavindraherat

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

AltLayer Airdrop Season One Update

🚀 Exciting Announcement!
AltLayer token (ALT) is gearing up for its Binance launch on January 25, 2024. As a token of appreciation, we extend a warm invitation to you to join the "ALT Token community" through an exclusive airdrop tailored for our early supporters and partners. Here's a quick overview:

Total Allocated ALT Tokens: 400,000,000 (4% of the total supply)

For a comprehensive breakdown of criteria and further details, refer to the complete announcement Oficial Website.
The window to Claim $ALT tokens is open from January 25 to February 08, 2024.
Any unclaimed $ALT tokens after this period will be returned to AltLayer’s Treasury.
We deeply appreciate your contribution to AltLayer's success! Stay tuned for more exciting developments in Season One.
Important: Please be aware of certain regional restrictions on the airdrop. Review the disclaimer before participating.
HackinwaleDev, @asoluwaseun, @ShawnJW, @Paiza28, @watai, @istaher, @Siorghlas, @far123123, @wycliffomwa, @ed1868, @TomiToivio, @kevin-hsin, @nsnull0, @faghani, @Mehranalam, @Songerius, @johnla, @sarunyousaklor, @felipeagger

AltLayer Airdrop Season One Update

🚀 Exciting Announcement!
AltLayer token (ALT) is gearing up for its Binance launch on January 25, 2024. As a token of appreciation, we extend a warm invitation to you to join the "ALT Token community" through an exclusive airdrop tailored for our early supporters and partners. Here's a quick overview:

Total Allocated ALT Tokens: 400,000,000 (4% of the total supply)

For a comprehensive breakdown of criteria and further details, refer to the complete announcement Oficial Website.
The window to Claim $ALT tokens is open from January 25 to February 08, 2024.
Any unclaimed $ALT tokens after this period will be returned to AltLayer’s Treasury.
We deeply appreciate your contribution to AltLayer's success! Stay tuned for more exciting developments in Season One.
Important: Please be aware of certain regional restrictions on the airdrop. Review the disclaimer before participating.

AltLayer Airdrop Season One Update

🚀 Exciting Announcement!
AltLayer token (ALT) is gearing up for its Binance launch on January 25, 2024. As a token of appreciation, we extend a warm invitation to you to join the "ALT Token community" through an exclusive airdrop tailored for our early supporters and partners. Here's a quick overview:

Total Allocated ALT Tokens: 400,000,000 (4% of the total supply)

For a comprehensive breakdown of criteria and further details, refer to the complete announcement Oficial Website.
The window to Claim $ALT tokens is open from January 25 to February 08, 2024.
Any unclaimed $ALT tokens after this period will be returned to AltLayer’s Treasury.
We deeply appreciate your contribution to AltLayer's success! Stay tuned for more exciting developments in Season One.
Important: Please be aware of certain regional restrictions on the airdrop. Review the disclaimer before participating.


Erase current selected object when input is blank

Newguy here,
I noticed that my users are trying to clear a current selected item by clicking on the ui-select, clearing the search box and then clicking out / escaping / hitting enter. This keeps the current item selected even though the search box is empty. Even with a delete button at the end of the input field, it still creates an awkward experience for the user as it does not perform as expected.
I think that there should be an option to clear the ng-model when the search box is empty and the user escapes the input.
For example, search for anything into the first ui-select in this plunker:
http://plnkr.co/edit/a3KlK8dKH3wwiiksDSn2?p=preview
After you've selected something, click on the ui-select again, and delete the search selection. Then, click outside of the input box. The previously selected item will appear again, even though this goes against what a user would expect to happen.
I have attempted to fix this on my own build but I lack the experience to properly do it. If anyone could help me figure this one out that would be great.
Thank you!

+1, I expirienced the same.

Closing this as a duplicate of #367


Generates warning about set-output command being deprecated

I used this action in a recent workflow and it generated a warning:

Warning: The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The fix should be to simply bump @actions/core to v1.10.0 as per https://github.com/mathiasvr/command-output/pull/5

bump - this would've been really useful if it worked with new github actions

@mathiasvr can you bump?


C++ log macro

Something like:
RERUN_LOG("path", …)
RERUN_LOG(rec, "path", …)
RERUN_LOG_TIMELESS(rec, "path", …)

The advantage is:
A) can early-out when rerun is disabled (#3754)
B) can automatic include file:line in the logging
Let's do this once we roll out file:line catching in all APIs

For C++20 there is std::source_location, and there might be compiler extensions for earlier C++ versions.


More meaningful termination types

Hey guys,
one thing that bothers me is that in production we often don't see why  some errors with different  termination types happened. What i would suggest is adding exception that triggered given type.
Proposal of which can be seen here: #3271
What do you think? It's a breaking change but i think it's for the better. If you like it i will finish it off and implement it with all the details.
Thanks

Closed by #3271.


Wallpaper Changer wont hide icons

im trying it on windows 10.....is there a Manual or Dictonary for the codes in Digi?

I'll take a look into it. Yes there are resources here:
-Digistump for the DigiSpark and their documentation: https://github.com/digistump/DigisparkArduinoIntegration/blob/master/libraries/DigisparkKeyboard/DigiKeyboard.h
-usb.org for the USB Usage IDs on page 53: http://www.usb.org/developers/hidpage/Hut1_12v2.pdf

Script executes as intended. Try modifying delays if on a slower machine


zz causes flickering in the end of file with wrapped lines

I came into this issue randomly, and was able to reproduce it only on a specific file.
When I move into the last line of the file that has wrapped lines and call zz, the scroll starts flickering.

How to reproduce:

init.lua:

local lazypath = vim.fn.stdpath "data" .. "/lazy/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
    vim.fn.system {
        "git",
        "clone",
        "--filter=blob:none",
        "https://github.com/folke/lazy.nvim.git",
        "--branch=stable",
        lazypath,
    }
end
vim.opt.rtp:prepend(lazypath)
require("lazy").setup {
    spec = {
        "karb94/neoscroll.nvim",
        config = function()
            require('neoscroll').setup {}
            local t = {}
            t['zz']    = {'zz', {'250'}}
            require('neoscroll.config').set_mappings(t)
        end
    },
}

create file with content:

short line
short line
long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line

long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line long line

short line
short line
short line
short line
short line
short line
short line
short line
short line
short line
short line
short line
short line
short line
short line
short line
short line

G, zz

I think this has something to do with wrap option: the bug occurs when the wrapped line ends up at the top of the screen. Unfortunately, I don't know neovim enough to debug it further.

I think I fixed this with 21d5297. Can you confirm?
The issue was that wrapped lines sometimes force you to scroll more lines than necessary and Neoscroll would try to backtrack which could result in an endless loop. Backtracking is not something it should do anyways so this change prevents backtracking one overshooting the target line.

Yes, now this works as expected.


OCIO :: Colorspace in filename :: Nuke

In GitLab by @kekefreedog on Apr 20, 2023, 17:47

From Kevin Zarshenas (230420)

Need
We need a tokken (cf #ref) called "colorspace" wich retrieve the colorspace information from Nuke.
Where can we find the colorspace ?!?
In Nuke, colorspace of output will depend of the "create write". You will find the colorspace used for each Create here in the OpenPype Settings :
{project} -> Nuke -> Color Management (ImageIO) -> Nodes -> {createInstance} -> {name:colorspace}
How can I get the reel name of the colorspace
Now we have the colorspace name, you have to open the OCIO config that you can find here or here in OpenPype Settings :

Open the OCIO config and check if the colorspace has a key in roles

If yes : get the value of the key.
If not : keep the current value
Name can have space and other anomaly...
Just use the below code to convert the string to clean string
If underscores are allowed :
import re

input_str = "sRGB - Texture"
output_str = re.sub(r'[^a-zA-Z0-9_]+', '_', input_str)
print(output_str)  # Output: "sRGB_Texture"

else if underscores are not allowed :
import re

input_str = "sRGB - Texture"
output_str = re.sub(r'[^a-zA-Z0-9]+', '', input_str)
print(output_str)  # Output: "sRGBTexture"

Final
And voilà ! Colorspace name is now ready to be retrieve and insert into the render image name :)

After discussion with Olivier, the modification of the colorspace names will be managed as soon as we can set up OCIO>=2.0'


Cleanup agent directory sprawl

Is your feature request related to a problem?
Yeah so the agent right now has a bunch of directories that get created as part of the Dockerfile and then if you want to persist that data you have to mount each folder as an individual volume. One of them is even called tmp. How did this make it past code review? (Hint: I didn't do any code reviews when I wrote this stuff 🤣 ). This is mostly a holdover from prior to going docker-only, when running ./setup-agent.sh could just create folders wherever it wanted on the host system.
Describe the feature you'd like
All persistent data should be mounted relative to a single directory that is separate from the application directory. Directory names should also be more descriptive (I'm lookin at you tmp)
I'll look towards @ajacques for guidance on how to make this good.

What are the different folders we use?

Right now data logs and tmp are all created relative to /opt/natlas/natlas-agent.
data optionally wouldn't be that important to save context, but there's a config option for NATLAS_SAVE_FAILS which saves all associated files if a particular scan fails to upload, which makes debugging easier. Logs probably should be persistent at least to some degree, they use a RotatingFileHandler  which I think already cleans up any logs older than 5 rotations (https://github.com/natlas/natlas/blob/main/natlas-agent/natlas/logging.py#L24)
tmp is basically only used to store the natlas-services file in that is referenced by the nmap binary as the list of ports to scan, and should be renamed. It's not a big deal to not persist this folder since it would just be fetched next start anyways.

Put it all in tmp/* in separate subfolders?
tmp/
   scans/
     {scan_id}/
   logs/ (12-factor app would suggest this goes to stdout anyway)
   natlas-services

tmp/ gets marked as read/writeable


Not able to run count(*) using hive inside the container

When I try to run a insert query or a select count(*) in hive which is an MR job the query is getting hung after a point. Below is the snippet.
hive> insert into test.counttest values(1,'Abc');
WARNING: Hive-on-MR is deprecated in Hive 2 and may not be available in the future versions. Consider using a different execution engine (i.e. spark, tez) or using Hive 1.X releases.
Query ID = root_20210531084134_915c8e72-1586-406a-8505-01af984ef376
Total jobs = 3
Launching Job 1 out of 3
Number of reduce tasks is set to 0 since there's no reduce operator

But I am able to execute a simple select query i am getting the output without any issues.

The container does not have yarn installed for executing map reduce queries using hive. You need to run that by setting the below  param before running your query
set mapreduce.framework.name=local; //default value is yarn
Using this you can execute your query by running mr job locally without use of yarn.
This issue is fixed in the latest commit where the setting has been added to mapredsite.xml file and reinstalling the whole setup will resolve your issue and also new release will be made for the same.


Childhood Immunizations HEDIS Measure

Related Tickets

SAR-76

How Things Worked (or Didn't) Before This PR
There was no CQL and associated files for Childhood Immunizations
How Things Work Now (And How to Test)
How it works now
I've added the CQL and associated files for Childhood Immunizations
Additionally, since the only differences between the exec files are the imports, I've created an exec file template
To test
run yarn to install the necessary packages
run node exec-files/exec-cis.js
Use your favorite diffchecker to confirm your output matches what is below
{
  'numer-EXM165-FHIR3': {
    Patient: FHIRObject {
      identifier: [Getter],
      active: [Getter],
      name: [Getter],
      telecom: [Getter],
      gender: [Getter],
      birthDate: [Getter],
      deceased: [Getter],
      address: [Getter],
      maritalStatus: [Getter],
      multipleBirth: [Getter],
      photo: [Getter],
      contact: [Getter],
      communication: [Getter],
      generalPractitioner: [Getter],
      managingOrganization: [Getter],
      link: [Getter],
      text: [Getter],
      contained: [Getter],
      extension: [Getter],
      modifierExtension: [Getter],
      id: [Getter],
      meta: [Getter],
      implicitRules: [Getter],
      language: [Getter]
    },
    'Qualifying Encounter': [ [FHIRObject] ],
    'Initial Population': true,
    'Denominator Exclusions': false,
    Denominator: 1,
    'DTaP Immunizations or Procedures': [
      [FHIRObject],
      [FHIRObject],
      [FHIRObject],
      [FHIRObject],
      [FHIRObject],
      [FHIRObject],
      [FHIRObject],
      [FHIRObject]
    ],
    'DTaP Vaccinations': [ [FHIRObject], [FHIRObject] ],
    'Hepatitis A Vaccinations': [ [FHIRObject] ],
    'Hepatitis B Immunizations or Procedures': [ [FHIRObject], [FHIRObject], [FHIRObject], [FHIRObject] ],
    'Hepatitis B Vaccinations': [ [FHIRObject], [FHIRObject] ],
    'HIB Immunizations or Procedures': [ [FHIRObject], [FHIRObject], [FHIRObject], [FHIRObject] ],
    'HIB Vaccinations': [ [FHIRObject], [FHIRObject] ],
    'Influenza Immunizations or Procedures': [ [FHIRObject], [FHIRObject], [FHIRObject] ],
    'Influenza Vaccinations': [ [FHIRObject], [FHIRObject] ],
    'IPV Immunizations or Procedures': [ [FHIRObject], [FHIRObject], [FHIRObject], [FHIRObject] ],
    'IPV Vaccinations': [ [FHIRObject], [FHIRObject] ],
    'Measles Indicators': [ [FHIRObject] ],
    'MMR Vaccinations': [ [FHIRObject] ],
    'Mumps Indicators': [ [FHIRObject] ],
    'Numerator Compliant DTaP Conditions': [ [FHIRObject] ],
    'Numerator Compliant IPV Conditions': [ [FHIRObject] ],
    'Numerator Compliant MMR Conditions': [ [FHIRObject] ],
    'Rubella Indicators': [ [FHIRObject] ],
    'Numerator Compliant HIB Conditions': [ [FHIRObject] ],
    'Numerator Compliant Hepatitis B Conditions': [ [FHIRObject] ],
    'VZV Vaccinations': [ [FHIRObject] ],
    'Numerator Compliant Varicella Zoster Conditions': [ [FHIRObject], [FHIRObject] ],
    'Pneumococcal Conjugate Immunizations or Procedures': [ [FHIRObject], [FHIRObject], [FHIRObject], [FHIRObject] ],
    'Pneumococcal Conjugate Vaccinations': [ [FHIRObject] ],
    'Numerator Compliant Pneumococcal Conjugate Conditions': [ [FHIRObject] ],
    'Numerator Compliant Hepatitis A Conditions': [ [FHIRObject], [FHIRObject] ],
    'Rotavirus 2 Dose Immunizations or Procedures': [ [FHIRObject], [FHIRObject] ],
    'Rotavirus 2 Dose Vaccinations': [ [FHIRObject] ],
    'Numerator Compliant Rotavirus Conditions': [ [FHIRObject] ],
    'Rotavirus 3 Dose Immunizations or Procedures': [ [FHIRObject], [FHIRObject], [FHIRObject] ],
    'Rotavirus 2 or 3 Dose Vaccinations A': [ [FHIRObject], [FHIRObject] ],
    'Rotavirus 2 or 3 Dose Vaccinations B': [],
    'Rotavirus 2 or 3 Dose Vaccinations C': [],
    'Rotavirus 2 or 3 Dose Vaccinations': [ [FHIRObject], [FHIRObject] ],
    'Rotavirus 3 Dose Vaccinations': [ [FHIRObject] ],
    'Numerator Compliant Influenza Conditions': [ [FHIRObject] ],
    Numerator: 1
  }
}

To Review
exec-cis.js - This is the exec file that actually does the work - there's not much to review here.
cis-codese.js - The list of codes in each value set. This is programmatically generated using the CQL from the VSAC API, so there's nothing to review here
cis.json - JSON version of the CQL created using the clinical_quality_language - nothing to review here
cis-patients.js - This contains the fake patients and their data. If you are really gung-ho, you can review the output of the results and confirm that the expressions with the CQL library returned the correct response based on the data, but that might take a while.
cis.cql - this is the main piece of the PR. Read through the following requirements, and as best you can, confirm that the CQL matches the guidelines. If you'd prefer, whenever you get to this portion I can send you the word doc these requirements are in, which might be easier than looking at screenshots.
Review the .cql file based on the HEDIS measures

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f2589f0). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #7   +/-   ##
=========================================
  Coverage          ?   91.82%
=========================================
  Files             ?       46
  Lines             ?     3828
  Branches          ?        0
=========================================
  Hits              ?     3515
  Misses            ?      313
  Partials          ?        0

Continue to review full report at Codecov.

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f2589f0). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #7   +/-   ##
=========================================
  Coverage          ?   91.82%
=========================================
  Files             ?       46
  Lines             ?     3828
  Branches          ?        0
=========================================
  Hits              ?     3515
  Misses            ?      313
  Partials          ?        0

Continue to review full report at Codecov.

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

The code works, and the tests perform as expected with the expected output, so I'm approving.
However:
I do get several hundred, or possibly a few thousand (I can't scroll back far enough to find the end) of these errors in the screenshot. I don't know if this is an artifact of the tests, but whatever it's doing we probably don't need to do without a conditional activation if it's expected to error like that nearly every time.

Ah good catch - I need to put a note about that. I've disabled that error locally, but it's an error message we're getting from an npm package, so it's not something that we can remove in a scalable way. We'll also disable logging in production, but I totally forgot that everyone else would get that error!

The code works, and the tests perform as expected with the expected output, so I'm approving.
However:
I do get several hundred, or possibly a few thousand (I can't scroll back far enough to find the end) of these errors in the screenshot. I don't know if this is an artifact of the tests, but whatever it's doing we probably don't need to do without a conditional activation if it's expected to error like that nearly every time.

Ah good catch - I need to put a note about that. I've disabled that error locally, but it's an error message we're getting from an npm package, so it's not something that we can remove in a scalable way. We'll also disable logging in production, but I totally forgot that everyone else would get that error!

Should we also add yarn.lock and package.json to the .gitignore file @TylerNoblett

Should we also add yarn.lock and package.json to the .gitignore file @TylerNoblett

I don't feel that we need to, personally - I looked at 5 of our other repos and only one of them had the 'lock' file ignored so going with convention I don't think we need to.
Also, a JS repo always includes package.json (that is how you know what packages to install etc). If you have a reason for wanting to ignore them, I'd be happy to hear it though!

Should we also add yarn.lock and package.json to the .gitignore file @TylerNoblett

I don't feel that we need to, personally - I looked at 5 of our other repos and only one of them had the 'lock' file ignored so going with convention I don't think we need to.
Also, a JS repo always includes package.json (that is how you know what packages to install etc). If you have a reason for wanting to ignore them, I'd be happy to hear it though!

Got it.  No reason. Im okay with leaving them then.


Add AWS org accounts provider

The only observation I have is that this appears to run every 5 minutes? no big deal right now but I guess at some point we should consider a) running this on different schedules b) surfacing provider / task schedules to the user and maybe the ability to explicitly run as we could probably poll way less frequently if the user could nudge these as needed (but this is massive tangent obvs).

Ah, yeah. I just added this as is to the example app. The schedule is configured externally from the provider so users can modify this to their liking.


Fixes compilation warning in InvariantDecimalModelBinderProvider

Please adjust your visual studio setting. We use space, not tab, and the indent should be 4 spaces


Reject requests with unsupported versions

Overview
This PR updates the version param validation logic to take a param of which versions are supported. As the validation logic was written before, it was happy to take any string as the version param, which led unexpected successes for versions that don't match
what the server is actually capable of.
Checklist

[x] Description of PR is in an appropriate section of the CHANGELOG and grouped with similar changes if possible

Demo
$ http :9000 service==wmts request==getcapabilities acceptVersions==1.0.1,1.1.0,1.1.2
HTTP/1.1 400 Bad Request
Content-Length: 50
Content-Type: text/plain; charset=UTF-8
Date: Mon, 15 Feb 2021 21:24:31 GMT

No available version in 1.0.0: 1.0.1, 1.1.0, 1.1.2

$ http :9000 service==wmts request==getcapabilities version==900
HTTP/1.1 400 Bad Request
Content-Length: 76
Content-Type: text/plain; charset=UTF-8
Date: Mon, 15 Feb 2021 21:31:59 GMT

Parameter 'version' has an invalid value of '900'. Needs to be one of: 1.0.0

Testing Instructions

bring up ogc-example project
make some GetCapabilities requests as above for wcs, wms, and wmts services using supported versions (1.1.1, 1.3.0, and 1.0.0, respectively)
make similar requests for unsupported versions (anything else)
make similar requests with acceptedVersions set to a comma-separated list that includes the valid version -- this should work
make similar requests with acceptedVersions set to a comma-separated list that excludes the valid version -- this should give you a 400

Closes #307

Thanks! Looks good to me! :+1:


Disabled CC26x2x7 yaml test

Disabled the Build example - TI CC26X2X6 yaml build due to failure for this PR.
Disabling as the problem is a lack of Flash on a specific device for a specific app.

Issue opened at https://github.com/project-chip/connectedhomeip/issues/26957


pull request for e2e test at 01/24/2017 02:15:09

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Missing Files in Dutch power resource folder

Hey, I don't know if you would reply to this, but there are files missing like, train_predictions, train_true and so on.
If you could upload them it would help a lot.

Hi
I have update the exectutionh section in README file. You would need to execute the lstm_predictor.py script to generate these files. Let me know if it helps.