0.10.57 and 0.10.58 broke the Julia Computing website

The blog section of our website did not compile correctly on both these versions. Just noting here to see if others have faced the same problem.

Thanks and sorry! I'll have a look

Ok here's the analysis:

blogpost pages at the end have {{recentblogposts}} this function calls pagevar to retrieve variables (like title, date) from other pages
at the initial pass, not all pages are seen, so pagevar(some_path) will trigger a conversion of the page some_path
since you have {{recentblogposts}} also on some_path, it does itself trigger pagevar and the order of operations means that this will cycle to stack overflow

I've now added a safety mechanism to avoid this happens; in a future version of Franklin this won't be needed.
Notes on the JC blog

It's not ideal to add the {{recentblogposts}} on every blog page, this should be part of the layout. I'll try to fix this and suggest the changes in a PR.
there's a bunch of other small errors with page variables that I'll also try to fix along the way

Thank you!


Need reference to recommended Telemetry schema

This topic very badly needs to include the Telemetry schemas as part of the Twin reported values as shown in this link.

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

ID: 8ff6fbb2-5679-a9e7-b9f3-40d638cadae8
Version Independent ID: fa51c99a-0df6-cebf-aecc-b08df5f85454
Content: Understand Azure IoT Hub device twins
Content Source: articles/iot-hub/iot-hub-devguide-device-twins.md
Service: iot-hub
GitHub Login: @fsautomata
Microsoft Alias: elioda

@JetstreamRoySprowl, your link is broken, or at least I cannot access it.

Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.


adding a new property to @Component decorator

I'm trying to use angular-css to add scoped component css to a project using ng-metadata, but I'm hitting a wall.
angular-css needs a string | string[] property on the component initialization. Like so;
{
   selector: 'divNg',
   templateUrl: 'tmpl.html',
   css: 'styles.css'
}

This is proving troublesome because the @Component decorator doesn't allow this property. Is there any way around this?

Sorry. Thought I posted this in the ng-metadata repository.


status of this project?

Looks like the last commit was in 2013. Is this project still maintained or should it be considered EOL?

tag @revuls

Hi @rbsmad, thank you for your message. I'm not actively maintaining the project.


Typo in aggregator?

https://github.com/hugobaudchon/geodataset/blob/a8616e9f1b10279f6f081e2910a192699c48fc78/geodataset/aggregator/aggregator.py#L97
Should this be    scores[score_name] = annotation[score_name] ?

Hi @melisandeteng, yes you're right! Thanks for catching this typo. It'll be fixed in the next version v0.1.3


CICD: npm autopulish success but not update

#https://github.com/npm/cli/issues/1637

https://github.com/npm/cli/issues/1637

https://github.com/npm/cli/issues/1637

npm/cli#1637

#https://github.com/npm/cli/issues/1637

#2

https://github.com/npm/cli/issues/1637

Error log below
npm notice
--
31 | npm ERR! code E404
32 | npm ERR! 404 Not Found - PUT https://registry.npmjs.org/tappay-typescript - Not found
33 | npm ERR! 404
34 | npm ERR! 404<EMAIL_ADDRESS>is not in the npm registry.
35 | npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
36 | npm ERR! 404
37 | npm ERR! 404 Note that you can also install from a
38 | npm ERR! 404 tarball, folder, http url, or git url.


[bug]: Exception in HostFunction: Value is undefined, expected a number

Describe the bug
I just want to run example app and only when i want to try KeyboardAwareScrollView i have this issue:
Code snippet
KeyboardAwareScrollView  from Examples/KeyboardAwareScrollView
Repo for reproducing
I would be highly appreciate if you can provide repository for reproducing your issue. It can significantly reduce the time for discovering and fixing the problem.
To Reproduce
Steps to reproduce the behavior:

Go to 'src/screens/Examples/'
yarn android

Expected behavior
This screenshot from version where had onContentTouch

Screenshots
After 1.5.8

Smartphone (please complete the following information):

Desktop OS: [Windows 10]
Device: [Android Emulator]
OS: [Android 12]
RN version: [ 0.71.11]
RN architecture: [old]
JS engine: [Hermes]
Library version: [^1.5.8]

Additional context
When I run the example in version 1.5.7 or earlier, it runs without issue. I don't know, am I missing something, or am I not running the example as expected, or is there something really wrong? I haven't tried it on v3 yet

@devoren are you running example project using 1.5.8? Could you elaborate a little bit more about your setup? Did you add 1.5.8 into your own project and trying to run KeyboardAwareScrollView from example project?
Right now KeyboardAwareScrollView depends on new functionality which is available in main branch, but hasn't been published to npm yet. Maybe it's the problem?

Right now KeyboardAwareScrollView depends on new functionality which is available in main branch, but hasn't been published to npm yet. Maybe it's the problem?

Hi @kirillzyusko Thank you for very quick reply! I think so. Maybe im silly, but i just download as zip and ran the example.
1.5.7 KeyboardAwareScrollView example:
https://github.com/kirillzyusko/react-native-keyboard-controller/assets/99968085/4b8d5cf1-2c8c-4559-bada-c15e25be173b

@kirillzyusko  While you're here, can I ask you one more thing? I don't understand this behaviour:

If I press the last input and scroll up, then when I close the keyboard it scrolls down (even if I press the first input before closing)
But if I press the first input and scroll down, it doesn't scroll back up again

https://github.com/kirillzyusko/react-native-keyboard-controller/assets/99968085/3e55bd4e-91e5-47bc-bc3c-fbc1b3326ea1

So if you are running 1.5.8 - it doesn't work, but 1.5.7 works?
Are you using git tags? Because version in main is not equal to 1.5.8 and version from main is not compatible with 1.5.8, since it's using new API.

If I press the last input and scroll up, then when I close the keyboard it scrolls down (even if I press the first input before closing)
But if I press the first input and scroll down, it doesn't scroll back up again

I think it's a bug and I think @IvanIhnatsiuk told me about this problem too. In fact there is a quite simple math in this component, you can try to debug and understand when you need to prevent scroll etc.
I'm currently working on new 1.6.0 version, which will have some improvements, so for now I'll postpone debugging/fixing this problem because it can be automatically fixed with new changes.
BTW @IvanIhnatsiuk did you find a solution for this problem?👀

@kirillzyusko Oh, you're right, this whole problem was due to me downloading with main instead of 1.5.8 tag and just messing it up. Thank You for this awesome library! ❤

@kirillzyusko No, I haven't found a solution to this problem yet, but I have some thoughts on how this can be fixed. So, I will have a look for a fix in the next few days 🙂


Installing the script with node on Shared Hosting

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
Hey, wonderful code.
I cloned this repo on my shared server with node and did all the istallation tasks.
How exactly can I now access my site?
🐻 Uptime-Kuma Version
idk
💻 Operating System and Arch
idk
🌐 Browser
idk
🐋 Docker Version
idk
🟩 NodeJS Version
14.10.1

Your server ip + 3001 port?


Implement double-spending checking and write unit test code

Add a member variable map to store Input objects into TransactionPool class.
Add the isValidTransaction function checking double-spending into TransactionPool class.
Add the code calling isValidTransaction of the TransactionPool into the acceptTransaction of the Ledger.
Add unit test code into agora.node.Ledger module.

I have a suggestion:
Replace the isValidTransaction in the TransactionPool. Move that check inside of the add method, and make the add method return a status code (true if the transaction was added).
Currently the abstraction is leaky. If we forget to call pool.isValidTransaction before calling pool.add(tx), then we will have added a double-spend transaction by mistake.

Also, the unittests should test the TransactionPool, not the Ledger. The Ledger already has tests for double-spend transactions. So I suggest moving the unittest into the TransactionPool module, where the only thing being tested is instantiating the Pool and trying to add double-spend transactions, and checking the contents of the transaction pool verifying no double-spend transactions were added.

Good work so far!

I fully understand all your comments, I'll try.

I already suggested replacing the Ledger unittest with a TransactionPool unittest in https://github.com/bpfkorea/agora/pull/356#issuecomment-534853592

I already suggested replacing the Ledger unittest with a TransactionPool unittest in #356 (comment)
Yes, I see. If I made a mistake, please understand.

Sure, I just didn't want you to do extra work on the review. :)

Ready for review.

Ready for review.

Ready for review.

The second commit should be squashed with the first. In general, when you want to merge changes in from the v0.x.x  branch, you have to rebase, not merge. For example, git pull --rebase origin HEAD

I believe there is one more part that needs to be updated, in Ledger.d in acceptTransaction:
public bool acceptTransaction (Transaction tx) @safe
{
        if (!this.pool.add(tx) || !this.isValidTransaction(tx))
        {
            log.info("Rejected tx: {}", tx);
            return false;
        }
}

After pulling new merged sources from Github and doing unit tests, I found out that there is some more work to do. It's related to the freezing capability. There is a case that same input can be included into a payment transaction and a freezing transaction. So the transanction pool have to use the tx type value to make the hash for inputs. I think It might take more time than expected.

There is a case that same input can be included into a payment transaction and a freezing transaction.

I don't think that should be possible? Once a UTXO is referenced by a transaction's input in the blockchain, it's no longer possible to reference it again. Can you show the code example which fails?

There is a case that same input can be included into a payment transaction and a freezing transaction.

I'm not sure I quite follow, too. The txtype shouldn't matter in that case, only if an output is referenced multiple times.

Sorry for my misunderstanding. Anyway, After appying Andrej's suggestion( https://github.com/bpfkorea/agora/pull/356#issuecomment-535324931), I found that the unittest relating to the freezing ability have failed. So, I'm now debugging it. The code failed at the Line 806 of agora/node/Ledger.d.
txes.each!((tx)     {         assert(ledger.acceptTransaction(tx) == is_valid);     });

@linked0 I think my suggestion was slightly wrong:
if (!this.pool.add(tx) || !this.isValidTransaction(tx))

This should be re-ordered, so this.isValidTransaction is checked first, and then this.pool.add.

It works. Thanks.

Excellent. Sorry for causing confusion!
Is the PR ready for another review now?

Yes. Just 20 minutes to ready to the PR. Would you please the reason why it works just by reordering the calls later?

Because in this case:
if (!this.pool.add(tx) || !this.isValidTransaction(tx))

A transaction will be added to the pool even if it's invalid. The pool itself doesn't do any transaction validation. So if you reorder them:
if (!this.isValidTransaction(tx) && !this.pool.add(tx))

Validation is done first, followed by transaction pool's duplicate transaction filtering.

Ready for review.

Because in this case:
if (!this.pool.add(tx) || !this.isValidTransaction(tx))

A transaction will be added to the pool even if it's invalid. The pool itself doesn't do any transaction validation. So if you reorder them:
if (!this.isValidTransaction(tx) && !this.pool.add(tx))

Validation is done first, followed by transaction pool's duplicate transaction filtering.

You mean "if (!this.isValidTransaction(tx) || !this.pool.add(tx))".
Just in order to avoid confusion.

Yes, that's right.

Fixes #301


implement order functinality

This PR makes it possible to for the User to change the Order in which Services/Webinterfaces are processed for a VMTemplate. This leads to Control over the resulting Cloud Config without having to delete Services/Webinterfaces just to create them again in the desired Order.

Looks good but isn’t there a component that is able to change order? (See courses when adding scenarios)?
if this is not working for this usecase this PR is fine


fix issue #41 - energiminer does not correctly switch epoch

Fixes #41

 Epoch switch not handled properly


Add HTTP basic auth option via ENV variables.

Make sure these boxes are checked( - [x] ) before submitting an issue.

[x] Running latest npm and node?
[x] The node_modules folder has right permissions
[x] Read issues.md
[x] Gone through existing open and closed issues.

I did not understand.
Where and how should I put
BASIC_AUTH_USER = user BASIC_AUTH_PWD = SecretPassword

You need to make it environment variables. Two ways you can do it:

Exporting before starting crontab-ui

export BASIC_AUTH_USER=user
export BASIC_AUTH_PWD=SecretPassword
crontab-ui

Adding before crontab-ui in the command

BASIC_AUTH_USER=user BASIC_AUTH_PWD=SecretPassword crontab-ui


ceph: rgw change the liveness probe url

to the RGWs swift objectstorage healthcheck api url [1]
which resolves an OCS false-positive CLBO of the RGW pod.
[1] https://docs.openstack.org/swift/latest/middleware.html#healthcheck
Signed-off-by: Mark Kogan<EMAIL_ADDRESS>(cherry picked from commit 3c807688fe6a5fe5ce342221a77aac9a955bfe98)
For https://bugzilla.redhat.com/show_bug.cgi?id=1768874

Wait for the first 4.2.z

Decision is go in 4.2


Karaoke lyrics in MIDI files sometimes are interpreted as Unicode

In an upcoming version of foo_midi I convert Soft Karaoke lyrics to a SYNCEDLYRICS tag. Most of the times the panel displays them correctly but sometimes the whole text is displayed as Unicode resulting in a bunch Japanese or Chinese glyphs.
The text is converted to UTF8 before it is added to the tag.
It think the panel gets confused when accented characters are encountered (e.g. in French or Spanish lyrics)

openlyrics should be preferring UTF-8 when loading lyrics.
Can you provide an example file that exhibits this behaviour for you? Can you provide debug output from the console for a reproduction of this issue?

I will attach an example after I release the next version of foo_midi. The only way to see it is by opening an example file with the component. The SYNCHEDLYRICS tag does not get written back to the MIDI file, for obvious reasons.

I did some checking: my own code was lying to me. In some cases the returned text was not valid UTF-8. After fixing it the test cases are displayed correctly now by your panel. Sorry to have bothered you.

Ah ok no problem, that's good to know. Thanks for confirming!


[Feature]: Employee Custom Screen

Connector Name
module/peoplehr (People HR)
Suggested feature
We have requirement to get custom screen data of an employee.
This is the API Support from People HR [1]
Following are the method required.

[1] https://apidocs.peoplehr.com/#tag/Employee-Custom-Screen
Related issues
No response

Closing as done


Way to add more dependencies as NextFederationPlugin internals

I'm working on a nextJS project with module federation. When I try to add react-redux, the host and remotes can not share the same ReduxContext on both client and server sides. The reason is the redux module has been initialized TWICE. I turned to use shared library to solve the client side issue with singleton: true. For server side, it always generates a react-redux bundle.
For testing purpose, I hack into the internal.js of NextFederationPlugin source code and add react-redux there, and everything works. It not only rekey the shared library but also exclude the library from bundle.
Is there anyway to achieve the same effect in plugin configuration?

for server you can share it as import: fasle, which would make it external.
I think in the next major version of this which im working on (check recent prs), you will have alot more proper control and MFP will work mostly like how it does outside of next

Try my new beta release, on the next tag on npm, it's the V7 branch and PR on my repo, see if that works

It doesn't really work for server side.
I added import: false for the dependency on the remote side. Then it complaints the Shared module doesn't exist in shared scope. On the host side, it first initiate the dependency from node_module then when loading the remote, it didn't look up the node_module but the sharing scope.
So I wonder is there a way to purely exclude the dependency from bundles and let webpack to look up the dependencies in local node_modules folder.
Any suggestion?


Back test loadUtils

As a developer we should have unit test to make sure that we don't break any functionality when we make alterations to the code base.

Resolved in #55


Adjust Navigation for PDF Export (EXPOSUREAPP-13438, EXPOSUREAPP-13439)

Quitting Export, Export errors and back navigation should all go back to personOverviewFragment
Ticket
Ticket

Navigation from the dialogs are ok. When pressing back from the pdf overview I would expect to see the info screen again, not the overview. Was that requested?

I agree. That's how the flow works for single certs exports. I'm not sure whether this was requested or not, but either way, both cases should behave the same imo.

Navigation from the dialogs are ok. When pressing back from the pdf overview I would expect to see the info screen again, not the overview. Was that requested?

Talked with Kerstin Jumpertz and implemented it accordingly to keep backstack on backnav


Dart mistakes stand-alone binary for aot snapshot

The file-type detection seems to be inconsistent here:
$ dart compile exe bin/hello_world.dart
Info: Compiling with sound null safety.
Generated: bin/hello_world.exe
$ dart bin/hello_world.exe # Thinks this is an aot snapshot
bin/hello_world.exe is an AOT snapshot and should be run with 'dartaotruntime'
$ dartaotruntime bin/hello_world.exe # does not agree this is an aot snapshot
Loading failed: Could not find isolate snapshot data.
VM initialization failed: Invalid vm isolate snapshot seen
$ bin/hello_world.exe  # Can invoke it directly
hello world

We're currently only checking for the ELF header bytes at the beginning of the file to try and determine if the target is an AOT snapshot. This obviously causes false positives when we try and pass an executable as the target for the VM, but I'm not sure if there's anything else we can easily check to differentiate between an AOT snapshot and an executable binary. @rmacnak-google, can you take a look?


HDF5 was not built with zlib while configuring netCDF-C

Hello,
I wanted to build the netCDF-C library from source and followed the tutorial from the official site, more precisely the sections "Building zlib from source", "Building hdf5 from source" and "Building netCDF-4 and the Remote Data Client from source". Based on these steps I created the following bash script:
#!/usr/bin/bash

# Definition of folders
ZDIR=/scratch/netcdf/zlib
H5DIR=/scratch/netcdf/hdf5
NCDIR=/scratch/netcdf/netcdf-c
NFDIR=/scratch/netcdf/netcdf-fortran
BUILDDIR=/scratch/netcdf/build

# Definition of versions
ZVER=1.2.11
H5VER=1.12.0
NCVER=4.7.4
NFVER=4.5.3

# Definition of compilers
export CC=/usr/bin/gcc
export CXX=/usr/bin/g++
export C++=/usr/bin/g++
export FC=/usr/bin/gfortran

# Build and install zlib
mkdir -p ${BUILDDIR}
cd ${BUILDDIR}
wget http://www.zlib.net/zlib-${ZVER}.tar.gz
tar -zxvf zlib-${ZVER}.tar.gz
rm zlib-${ZVER}.tar.gz
cd zlib-${ZVER}
./configure --prefix=${ZDIR}
make check #-j 4
make install

# Build and install hdf5
cd ${BUILDDIR}
wget https://hdf-wordpress-1.s3.amazonaws.com/wp-content/uploads/manual/HDF5/HDF5_${H5VER//./_}/source/hdf5-${H5VER}.tar.gz
tar -zxvf hdf5-${H5VER}.tar.gz
rm hdf5-${H5VER}.tar.gz
cd hdf5-${H5VER}
./configure --with-zlib=${ZDIR} --prefix=${H5DIR} --enable-hl
make check #-j 4
make install

# Build and install netcdf-c
cd ${BUILDDIR}
wget -O nc-${NCVER}.tar.gz https://github.com/Unidata/netcdf-c/archive/v${NCVER}.tar.gz
tar -zxvf nc-${NCVER}.tar.gz
rm nc-${NCVER}.tar.gz
cd netcdf-c-${NCVER}
CPPFLAGS='-I${H5DIR}/include -I${ZDIR}/include' LDFLAGS='-L${H5DIR}/lib -L${ZDIR}/lib' ./configure --prefix=${NCDIR}
make check #-j 4
make install

## Build and install netcdf-fortran
## define environment variables
#export LD_LIBRARY_PATH=${NCDIR}/lib:${LD_LIBRARY_PATH}
#
## go into builddir
#cd ${BUILDDIR}
#wget -O nf-${NFVER}.tar.gz https://github.com/Unidata/netcdf-fortran/archive/v${NFVER}.tar.gz
#tar -zxvf nf-${NFVER}.tar.gz
#rm nf-${NFVER}.tar.gz
#cd netcdf-fortran-${NCVER}
#CPPFLAGS='-I${NCDIR}/include LDFLAGS=-L${NCDIR}/lib' ./configure --prefix=${NFDIR}
#make check #-j 4
#make install

# Go back to builddir
cd ${BUILDDIR}

The building of zlib and HDF5 works fine, but the ./configure-command in the installation of netCDF-C fails due to the following error:
configure: error: HDF5 was not built with zlib, which is required. Rebuild HDF5 with zlib.
make: * No rule to make target 'check'.  Stop.
make: * No rule to make target 'install'.  Stop.

I cannot explain this, because hdf5 seems to be explicitly compiled with zlib. What did I miss in my script?
Operating system is CentOS 8 with GNU GCC 8.3.1 and GNU Make 4.2.1.
Best regards,
Gabriel

When configure runs it produces an output file called config.log.
Can you attach that output file to this issue? Or look in it for the relevant section where this failure occurs and post that?

Here is the config.log produced by netcdf-c: config.log
Do you also need the config.log from HDF5?

OK, this is a bug that has been fixed for the next release.
Go into the directory where the HDF5 header files are, and create an empty file with the name H5pubconf.h.
Then try to run configure again and see if it works.

Unfortunately, in the include directory of HDF5 there exists already a file named H5pubconf.h:
# pwd
/scratch/netcdf/hdf5/include
# ls
H5ACpublic.h  H5Epublic.h   H5FDmpio.h     H5Gpublic.h   H5Opublic.h   H5Rpublic.h               H5VLpassthru.h
H5api_adpt.h  H5ESpublic.h  H5FDmulti.h    H5IMpublic.h  H5overflow.h  H5Spublic.h               H5VLpublic.h
H5Apublic.h   H5FDcore.h    H5FDpublic.h   H5Ipublic.h   H5PLextern.h  H5TBpublic.h              H5Zpublic.h
H5Cpublic.h   H5FDdirect.h  H5FDros3.h     H5LDpublic.h  H5PLpublic.h  H5Tpublic.h               hdf5.h
H5DOpublic.h  H5FDfamily.h  H5FDsec2.h     H5Lpublic.h   H5Ppublic.h   H5version.h               hdf5_hl.h
H5Dpublic.h   H5FDhdfs.h    H5FDstdio.h    H5LTpublic.h  H5PTpublic.h  H5VLconnector.h
H5DSpublic.h  H5FDlog.h     H5FDwindows.h  H5MMpublic.h  H5pubconf.h   H5VLconnector_passthru.h
H5Epubgen.h   H5FDmpi.h     H5Fpublic.h    H5Mpublic.h   H5public.h    H5VLnative.h

(I compiled all libraries with make -j 4, because make check took very long.)

Then WTF can't if compile it? Stand by...

You are setting CPPFLAGS like this:
ac_cv_env_CPPFLAGS_value='-I${H5DIR}/include -I${ZDIR}/include'
Do you have H5DIR and ZDIR defined?

I'm running the script above, and H5DIR and ZDIR should be defined.

I had the same issue.
hdf5 is built with zlib, and yet configures gives me the same error reported by gabriel2029.
Any suggestions/fixes?
Thank you,
Gus Correa

Hello Gus,
I solved this problem at first by using an older netCDF-C-version, after that by switching to MPI and some further parameter adjustments. My last working standing should be the following, however, I haven't looked for it quite a while: install_netcdf_gnu.sh.txt, install_netcdf_intel.sh.txt
Especially the links used in the script could be outdated.
An easier way could be directly the usage of the spack package manager https://spack.io/, which enables you to build the most common packages with the compiler of your choice. But here you have to invest time in understanding the setup process.
Best regards,
Gabriel

Thank you Gabriel.
Somehow netCDF-C 4.8.0 builds without a problem (but using it to build
netCDF-fortran 4.5.3 still didn't work, trying more ...)
It is the Fortran-90 API that I am trying to get working.
The one from the Linux package is throwing an error in nf90_def_var_fill
during compilation that
sounds very much as a bug (mindset that the last parameter, the actual
_FillValue must be a 4-byte integer).
But netCDF-C 4.7.4 doesn't build.
I am surprised because the autotools should work smoothly, since
everything is built with Gnu compilers (including hdf5, etc which are
native Linux packages).
Not so long ago netCDF would bundle the C, Fortran and C++ APIs in a single
and self-consistent tarball,
with a release number, and everything would build smoothly, user-friendly.
I miss that.
Gus Correa
On Thu, Jul 8, 2021 at 6:17 PM gabriel2029 @.***> wrote:

Hello Gus,
I solved this problem at first by using an older netCDF-C-version, after
that by switching to MPI and some further parameter adjustments. My last
working standing should be the following, however, I haven't looked for it
quite a while: install_netcdf_gnu.sh.txt
https://github.com/Unidata/netcdf-c/files/6787513/install_netcdf_gnu.sh.txt,
install_netcdf_intel.sh.txt
https://github.com/Unidata/netcdf-c/files/6787514/install_netcdf_intel.sh.txt
Especially the links used in the script could be outdated.
An easier way could be directly the usage of the spack package manager
https://spack.io/, which enables you to build the most common packages
with the compiler of your choice. But here you have to invest time in
understanding the setup process.
Best regards,
Gabriel
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Unidata/netcdf-c/issues/1844#issuecomment-876780844,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHIZALWO2EOLUMZL233TPLLTWYPWJANCNFSM4RTXOWFQ
.

For those of you using cmake, I had the same issue building netcdf-c-4.8.1 with hdf5-1.12.1. Changing
CHECK_C_SOURCE_COMPILES("#include <H5public.h>
in CMakeLists.txt, line 834 to
CHECK_C_SOURCE_COMPILES("#include <H5pubconf.h>
solved the issue for me.

I believe this issue can be closed.


Raise exceptions better

We're currently using a MackValidationError which isn't great because it makes some of the functions hard to copy / paste.  If you want to copy / paste the drop_duplicates function into your codebase, you also need to copy / paste the MackValidationError.
In other parts of the code, we're doing raise Exception, which I think is an antipattern.
I think raise TypeError is the correct path forward here.  We might want to change the validation logic from if not delta_table to if not isinstance(delta_table, DeltaTable).
Per the Python docs

a TypeError should be "Raised when an operation or function is applied to an object of inappropriate type."
a ValueError should be "Raised when an operation or function receives an argument that has the right type but an inappropriate value, and the situation is not described by a more precise exception such as IndexError."

I think TypeError should handle the existing validation checks.

This is fixed, thanks @robertkossendey


Provide license

Although reusing the queries and datasets are permitted to some extent by "fair use", it's better to provide public license for your repo.
Example:
To the extent possible under law, the author(s) have dedicated all copyright and related and neighboring rights to this software to the public domain worldwide. This software is distributed without any warranty.
You should have received a copy of the CC0 Public Domain Dedication along with this software. If not, see <http://creativecommons.org/publicdomain/zero/1.0/>.

Thanks, added MIT License.


podman: make work on darwin

podman: Use path to find gvproxy on Darwin
Revert "podman: remove darwin wrapper"

Motivation for this change
Make podman work on Mac.
This is a temporary solution to #141041, with notes on how to work with upstream's change once 4.0.0 is released.
This restores the wrapper for darwin.  @zowoq mentions that this wrapper somehow wrote to the store, but I don't
see how that could be unless there is a problem with one of packages passed to lib.makeBinPath (in which case
removing the wrapper isn't the right fix).
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] 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

[x] Fits CONTRIBUTING.md.

@marsam @zowoq

Also the podman maintainers have previously discussed this sort of patching and we really don't want to carry what will basically be a permanent patch.
It may not seem like much to add the patch but needing to keep the podman, etc ecosystem in sync and up to date makes permanent patching problematic.
podman used find gvproxy from $PATH until upstream changed it to what was basically the worst possible option for us, it would really be for the best that it get resolved upstream.

Hold up.  I'm very confused.
So the package is broken and doesn't work on darwin, so we are removing the wrapper -- which AFAICT is unrelated to the breakage, but breaks it further.  But we neither mark the package as broken nor remove darwin from its supported platforms?
And this solution contains a patch literally labelled "temporary", with a reference to the already-merged upstream fix, and instructions for when the already-merged upstream fix is released, but you are closing it because we won't carry permanent patches?
I can understand many reasons for not wanting to merge this, but your stated reasons don't make sense.  Did you read the code?

But we neither mark the package as broken nor remove darwin from its supported platforms?

podman can still be used as a remote, it's only podman machine (which by having the wrapper implies that we support it) that is broken.

Aha, I get it.  Sorry for the grumpy.

4.0 update is merged, PR to wrap gvproxy: https://github.com/NixOS/nixpkgs/pull/161130


chore(npm): use bin.sh for execute

Summary
Reduce execution startup time
This should solve few issues related to bun and it has a bunx/npx support compared to #2359
This script, bin.sh executes only as later it will be replaced to actual binary file
This approach does not work on pnpm and does not reduce startup time. For npx it is faster but not much, for bunx it is marginally faster
Test Plan
Faster startup time, saving CPU-time and power for small and medium projects
Benchmark

Command for test: hyperfine --warmup 2 --runs 3 'bunx dalisoft/biome-rs-npm#v1.8.3' 'bunx @biomejs/biome' --export-markdown biome-npx.md

Command
Mean [ms]
Min [ms]
Max [ms]
Relative

bunx dalisoft/biome-rs-npm#v1.8.3
4.9 ± 0.1
4.9
5.0
1.00

bunx @biomejs/biome
45.3 ± 0.1
45.2
45.4
9.20 ± 0.13

Has it been tested on windows?
Has it been tested on MUSL operating systems?
What bun issues are you talking about? It would be great if you could point to an issue, or explain them.

ESbuild uses only a postinstal script. I wonder if we could use it as an inspiration.

@Conaclos Yes, that way could reduce startup time

@arendjr

It feels like a risky change to me. My first questions would be, how does this affect Windows support and has it been tested with Yarn PnP?

Not, not tested yet with Windows and Yarn PnP

@ematipico

Has it been tested on windows?

Not yet

Has it been tested on MUSL operating systems?

Not yet

What bun issues are you talking about? It would be great if you could point to an issue, or explain them.

I mean #2359 which did not worked bunx/npx but now working with bin.sh script

The linked issue/pr doesn't say anything about bunx or npx. So I ask again if you can explain the issue

It is not @biomejs bug. It is just reference to issue which (previously) i'm made PR for reduce startup time attempt bug that not worked with bunx or npx so this solution works (see https://github.com/oxc-project/oxc/pull/2920#issuecomment-2042849455)

Closing for now, as this wasn't tested on other OS and with other package managers.
Also, the bash code is more convoluted than the Node.js code, and I risk it could introduce more friction in terms of contributions.
Feel free to open a discussion to discuss this alternative, if you want, and why we should accept this change.


Enhanced path-alias

Currently we can map single specific legacy URLs to a specific entry or to a category template. It would also be great if we could map a legacy URL via some higher-level scripting functionality from the templates directly.
On beesbuzz.biz I have this in my main.py to do a quick-and-dirty version of this:
@app.route('/d/<int:date>.php')
def redirect_date(date):
    return flask.redirect(flask.url_for('category', category='comics', date=date))

but it would be great if this could be supported more directly in Publ itself.

Originally I was planning on adding a Path-Alias-Regex header but that gets unwieldy fast. What would be better is simply making that above @app.route rule something that can be more easily injected at an API level from your application main, for example:
@publ.add_path_regex(app, r'/d/([0-9]+)\.php')
def redirect_date(match):
    return flask.url_for('category', category='comics', date=match.group(1))

@publ.add_path_regex(app, r'/d/([0-9]+)_([0-9]+).php')
def redirect_week(match):
    return flask.url_for('category',category='comics',date='{}w{}'.format(match.group(1,2)))

Fixed in #114


Save source viewColumn for previews, fixes #74008

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

Thanks! Will be in the next insiders build and is scheduled to go out with VS Code 1.37


av-script: honor script.sh logic for AppVeyor too

Could you explain what this does? $APPVEYOR_REPO_TAG_NAME is never set in Travis CI.

Yeah I only realised this now. I somehow expected appveyor to run some of the .sh scripts in ci/.
Not sure why I ever expected that…


Untrack build files and folders

Currently the repository tracks build files and folders which makes the repository size quite large for a small project. cloning the project too can be slow. I'm proposing that we stop tracking the build files and folders. The project can be built locally and the resulting binaries published in the releases.

I see. I'll send in a pr later today to ignore those files and folders. so you can build locally. I'll build mine too locally and share the final binary with you so you can create a release. Do you think a cli is necessary?

A CLI will work, I have fixed them already just still having issues with pushing out to GitHub. It kept complaining about large files.

Also, I won't accept your PR for renaming because I changed it.

Can you send a screenshot of you project tree so I see what needs to be ignored?

You changed your number already. Please call me.

I've sent a pr with a fix


Bump default node count and instance types

Move from n1-standard-2 with 2 vCPU and 7Gbi to n2-standard-4 with 4 vCPU and 16Gbi. Otherwise there is not enough CPU for everything deployed on an MC
Bump control-plane nodes to 3 and worker nodes to 4, to be more alinged with AWS and Azure MCs

Just one comment for the future: to be even more in-line with how we do things on AWS we should set 3 different machineDeployments, each in a different availability zone.


Docs: Update CookieConsent library and embed it's JS to docs.js

Description
addresses this issue: https://github.com/BytexDigital/BytexDigital.Blazor.Components.CookieConsent/issues/32
How Has This Been Tested?
Manually
Type of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation (fix or improvement to the website or code docs)

Checklist

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.

Seems like it works vs not working on dev branch

Seems like it works vs not working on dev branch

Is this good to be merged then? I fixed the JS so it shouldn't show any error in console.


remove duplicate Link to https://github.com/cloudamqp/amqp-client.js

The link to https://github.com/cloudamqp/amqp-client.js is included several times in the documentation. This pull request removed the second place.

@AnWeber Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@AnWeber Thank you for signing the Contributor License Agreement!

@michaelklishin thx


Made CI changes

Added github actions
Updated badges
Removed Travis CI

I don't see a GitHub action kicking off?

could that be because it is not in master yet?

Codecov Report

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

@@             Coverage Diff              @@
##             master     #302      +/-   ##
============================================
- Coverage     90.08%   90.00%   -0.08%
+ Complexity     1441     1438       -3
============================================
  Files           249      249
  Lines          3943     3943
  Branches        191      191
============================================
- Hits           3552     3549       -3
- Misses          340      343       +3
  Partials         51       51

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/com/vonage/client/sns/SnsClient.java
60.00% <0.00%> (-40.00%)
1.00% <0.00%> (-2.00%)

...c/main/java/com/vonage/client/sns/SnsEndpoint.java
97.91% <0.00%> (-2.09%)
16.00% <0.00%> (-1.00%)

@yallen011 - It looks like the windows machine is not replacing the -----BEGIN PRIVATE KEY----- correctly from the keys and a - is bleeding into the private key it's trying to parse (hence the 2d illegal character - which it's reading as 2d).
My guess is that this is an issue in the JWT library - which is assuming the line ending type of the first line.
see: https://www.prostdev.com/post/understanding-the-illegal-base64-character-error-java-groovy-and-mule-4-dw-2-0


PANIC: 1

Hi Prisma Team! My Prisma Client just crashed. This is the report:
Versions

Name
Version

Node
v12.5.0

OS
darwin

Prisma Client
2.13.1

Logs
prisma-client { clientVersion: '2.13.1' }
plusX Execution permissions of /Users/pieter/Invisible/invisible/node_modules/.prisma/client/query-engine-darwin are fine
plusX Execution permissions of /Users/pieter/Invisible/invisible/node_modules/.prisma/client/query-engine-darwin are fine

Some more info after adding DEBUG=prisma-client,engine
[=== ] info  - Generating static pages (4/19)2020-12-30T11:45:44.629Z engine stdout {
  timestamp: 'Dec 30 13:45:44.628',
  level: 'ERROR',
  fields: {
    message: 'PANIC',
    reason: '1',
    file: 'query-engine/core/src/interpreter/query_interpreters/nested_read.rs',
    line: 78,
    column: 56
  },
  target: 'query_engine'
}
2020-12-30T11:45:44.630Z engine TypeError: this.currentRequestPromise.cancel is not a function
    at NodeEngine.handlePanic (/Users/pieter/Invisible/invisible/node_modules/@prisma/client/runtime/index.js:26799:36)
    at EventEmitter.<anonymous> (/Users/pieter/Invisible/invisible/node_modules/@prisma/client/runtime/index.js:26733:18)
    at EventEmitter.emit (events.js:200:13)
    at LineStream.<anonymous> (/Users/pieter/Invisible/invisible/node_modules/@prisma/client/runtime/index.js:27039:33)
    at LineStream.emit (events.js:200:13)
    at addChunk (_stream_readable.js:294:12)
    at readableAddChunk (_stream_readable.js:275:11)
    at LineStream.Readable.push (_stream_readable.js:210:10)
    at LineStream.Transform.push (_stream_transform.js:150:32)
    at LineStream._pushBuffer (/Users/pieter/Invisible/invisible/node_modules/@prisma/client/runtime/index.js:24043:19) {"timestamp":"Dec 30 13:45:44.628","level":"ERROR","fields":{"message":"PANIC","reason":"1","file":"query-engine/core/src/interpreter/query_interpreters/nested_read.rs","line":78,"column":56},"target":"query_engine"}
2020-12-30T11:45:44.632Z engine {
  error: SocketError: closed
      at Socket.onSocketClose (/Users/pieter/Invisible/invisible/node_modules/@prisma/client/runtime/index.js:25189:33)
      at Socket.emit (events.js:200:13)
      at Pipe.<anonymous> (net.js:588:12) {
    name: 'SocketError',
    code: 'UND_ERR_SOCKET'
  }
}
2020-12-30T11:45:44.635Z prisma-client Error: PANIC: 1

This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.

https://github.com/prisma/prisma-client-js/issues/new?body=Hi+Prisma+Team%21+My+Prisma+Client+just+crashed.+This+is+the+report%3A%0A%23%23+Versions%0A%0A%7C+Name++++++++++++%7C+Version++++++++++++%7C%0A%7C-----------------%7C--------------------%7C%0A%7C+Node++++++++++++%7C+v12.5.0++++++++++++%7C+%0A%7C+OS++++++++++++++%7C+darwin+++++++++++++%7C%0A%7C+Prisma+Client+++%7C+2.13.1+++++++++++++%7C%0A%0A%0A%0A%23%23+Logs%0A%60%60%60%0Aprisma-client+%7B+clientVersion%3A+%272.13.1%27+%7D%0Aprisma-client+Prisma+Client+call%3A%0Aprisma-client+prisma.role.findMany%28%7B%0A++include%3A+%7B%0A++++users%3A+%7B%0A++++++select%3A+%7B%0A++++++++id%3A+true%0A++++++%7D%0A++++%7D%0A++%7D%0A%7D%29%0Aprisma-client+Generated+request%3A%0Aprisma-client+query+%7B%0A++findManyRole+%7B%0A++++id%0A++++name%0A++++users+%7B%0A++++++id%0A++++%7D%0A++%7D%0A%7D%0A%0AplusX+Execution+permissions+of+%2FUsers%2Fpieter%2FInvisible%2Finvisible%2Fnode_modules%2F.prisma%2Fclient%2Fquery-engine-darwin+are+fine%0AplusX+Execution+permissions+of+%2FUsers%2Fpieter%2FInvisible%2Finvisible%2Fnode_modules%2F.prisma%2Fclient%2Fquery-engine-darwin+are+fine%0A%60%60%60&title=PANIC%3A+1&template=bug_report.md

If you want the Prisma team to look into it, please open the link above 🙏

    at NodeEngine.handleRequestError (/Users/pieter/Invisible/invisible/node_modules/@prisma/client/runtime/index.js:26642:21)
    at /Users/pieter/Invisible/invisible/node_modules/@prisma/client/runtime/index.js:27295:36
    at processTicksAndRejections (internal/process/task_queues.js:82:5)
    at async PrismaClientFetcher.request (/Users/pieter/Invisible/invisible/node_modules/@prisma/client/runtime/index.js:78094:24)

Error occurred prerendering page "/permissions". Read more: https://err.sh/next.js/prerender-error
Error:
Invalid `prisma.role.findMany()` invocation:

  PANIC: 1

This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.

https://github.com/prisma/prisma-client-js/issues/new?body=Hi+Prisma+Team%21+My+Prisma+Client+just+crashed.+This+is+the+report%3A%0A%23%23+Versions%0A%0A%7C+Name++++++++++++%7C+Version++++++++++++%7C%0A%7C-----------------%7C--------------------%7C%0A%7C+Node++++++++++++%7C+v12.5.0++++++++++++%7C+%0A%7C+OS++++++++++++++%7C+darwin+++++++++++++%7C%0A%7C+Prisma+Client+++%7C+2.13.1+++++++++++++%7C%0A%0A%0A%0A%23%23+Logs%0A%60%60%60%0Aprisma-client+%7B+clientVersion%3A+%272.13.1%27+%7D%0Aprisma-client+Prisma+Client+call%3A%0Aprisma-client+prisma.role.findMany%28%7B%0A++include%3A+%7B%0A++++users%3A+%7B%0A++++++select%3A+%7B%0A++++++++id%3A+true%0A++++++%7D%0A++++%7D%0A++%7D%0A%7D%29%0Aprisma-client+Generated+request%3A%0Aprisma-client+query+%7B%0A++findManyRole+%7B%0A++++id%0A++++name%0A++++users+%7B%0A++++++id%0A++++%7D%0A++%7D%0A%7D%0A%0AplusX+Execution+permissions+of+%2FUsers%2Fpieter%2FInvisible%2Finvisible%2Fnode_modules%2F.prisma%2Fclient%2Fquery-engine-darwin+are+fine%0AplusX+Execution+permissions+of+%2FUsers%2Fpieter%2FInvisible%2Finvisible%2Fnode_modules%2F.prisma%2Fclient%2Fquery-engine-darwin+are+fine%0A%60%60%60&title=PANIC%3A+1&template=bug_report.md

If you want the Prisma team to look into it, please open the link above 🙏

    at PrismaClientFetcher.request (/Users/pieter/Invisible/invisible/node_modules/@prisma/client/runtime/index.js:78129:15)
    at processTicksAndRejections (internal/process/task_queues.js:82:5)
2020-12-30T11:45:44.642Z engine Restart attempt 1. Waiting for backoff
2020-12-30T11:45:44.642Z engine Restart attempt 1. Backoff done
2020-12-30T11:45:44.643Z engine { cwd: '/Users/pieter/Invisible/invisible/libs/flow-data/prisma' }
2020-12-30T11:45:44.643Z engine Search for Query Engine in /Users/pieter/Invisible/invisible/node_modules/.prisma/client
2020-12-30T11:45:44.644Z engine {
  flags: [
    '--enable-raw-queries',
    '--unix-path',
    '/tmp/prisma-28b1c18fec34781f741ff8e6.sock'
  ]
}
2020-12-30T11:45:44.653Z prisma-client Prisma Client call:
2020-12-30T11:45:44.653Z prisma-client prisma.role.findMany(undefined)
2020-12-30T11:45:44.653Z prisma-client Generated request:
2020-12-30T11:45:44.653Z prisma-client query {
  findManyRole {
    id
    name
  }
}

Also, I am experiencing this locally, inside github actions and in vercel. Everything worked fine and then suddenly it changes

Was it working with the same version 2.13.1 or did it break after an upgrade?

Worked with 2.13.1
I've realized that the issue is only on the staging DB and not on my local one. It only failed on a particular next page which called
prisma.role.findMany({
    include: { users: { select: { id: true } } },
  });

Removing the include fixed the issue, so I looked into the auto-created _RoleToUser table which had 3 rows
A | B
1 | 1
2 | 2
3 | 2

(user 1 had admin role and user 2 had the other 2 roles)
I deleted those 3 entries and added the include back and it worked. I then opened prisma studio, reassigned the roles and it worked again. So there must've been some hidden entries or something that I could not see in prisma studio or via psql that had that table messed up.
I did run some manual migrations a day or so before this occurred, so many the prisma migrate deploy broke staging and I only realized it by the time the data and queries aligned to produce the error.
What would be nice is if prisma could give some more concrete errors. There's no underlying sql error being exposed here. It was not even clear that the issue was on the join table or calling include. All I knew was that a particular nextjs page was failing in SSG and I had to go from there.

Looks like a duplicate of https://github.com/prisma/prisma-client-js/issues/955
I will wait for that to be fixed here.

Looks like a duplicate of https://github.com/prisma/prisma-client-js/issues/955
I will wait for that to be fixed here.


docs: Merged CI guides

This commit merges the following three language-specific guides, related to using Dagger in CI, into a single multi-language guide.
Relates to #4574.

Merged @vikram-dagger ! Thank you!
followup opened
https://github.com/dagger/dagger/issues/4943


Stale data in verification-metadata (was: log4j vulnerability)

ktlint seems to reference a vulnerable log4j version
https://github.com/pinterest/ktlint/search?q=log4j
But it doesn't seem like it's actually used.
Updating the version or removal of the entries would help a lot.
Source: https://logging.apache.org/log4j/2.x/security.html
Update: I'm seeing this in the binary
strings ktlint | grep -i log4j
org/jetbrains/kotlin/org/apache/log4j/
org/jetbrains/kotlin/org/apache/log4j/Level.class
org/jetbrains/kotlin/org/apache/log4j/Priority.class
...

thanks @pvegh. the vulnerable log4j was used in an older version of the shadowJar plugin. It's since been upgraded, but it's referenced in stale gradle verification metadata.

Closed by #1317


The library does not update to the updated data structure if the JSON has array

Issue type
I'm submitting a (check one):
[ ] Bug report
[ ] Feature request
[ ] Regression (something that used to work, but stopped working in a newer version)
[X] Support request
[ ] Documentation issue or request
Prerequisites
Before posting, make sure you do the following (check all):
[X] Confirm you are using the latest versions of all necessary packages (or if not, explain why not)
[X] Search GitHub for a similar issue or PR
[X] If submitting a Support request, also search Stack Overflow for similar issues
Note: Please cross-post GitHub support requests to Stack Overflow, and include a link in your GitHub issue to your Stack Overflow question. We do currently respond to support requests on GitHub, but we eventually expect to stop, and will then refer all support questions exclusively to Stack Overflow.
Current behavior
The form does not refresh showing the correct elements when the JSON is passed dynamically. When the page is loaded I am sending the JSON with set of array elements (say the size is 5). But on clicking a button, i change the data and the JSON is updated to set of array elements (say the size is 4). The JSON schema form does not update and show only the 4 elements, it preserves the old values too.
Expected behavior
When the value is updated dynamically, the Angular Schema Form should update dynamically reflecting the updated values.

IMPORTANT: How can we reproduce your problem?
The demo of the issue can be found at https://stackblitz.com/edit/angular-le4ngp.

Environment
OS name & version: Windows 7
Browser name & version: Chrome
Angular version: 5
Angular JSON Schema Form version(s): 2
Other relevant software or packages:

Any other relevant information

Check this workaround:
https://stackblitz.com/edit/angular-ye3vre
Use ngIf states for hide/show form.

Thanks this workaround fixes my issue


Mount & Blade II: Bannerlord works well

Using dlsstweak's default dxgi.dll, DLSS 3.1.1 dll, and ForceDLAA setting = true, DLAA is working for Bannerlord. Works in singleplayer and any multiplayer mod which does not use BattlEye anti cheat (works fine in cRPG mod). Trying to launch native multiplayer Bannerlord will crash because of BattlEye flagging the dxgi.dll.
Visual quality is great and does not suffer from the same scaling/ghosting problems that current patch Bannerlord has when using dlss.

Added to the wiki, thanks for the info :+1:


Prepare the landing pages

Make all 21 guides landing pages have the production content and same in both new staging SN and production SN

The final 5 guides have had landing pages created on the production and staging portals, pending review.


[Toolchain] Change inference function name

This commit changes inference() to infer().
ONE-vscode-DCO-1.0-Signed-off-by: Jiyoung Yun<EMAIL_ADDRESS>Related issue: #1562

@jyoungyun , changing API will break codes outside of this REPO if any.
It would be better to (1) add infer() (2) notify users to change codes before YY/MM (3) deprecate inference() at YY/MM.
I'll land this if you are sure changing this API is OK.

@seanshpark

@jyoungyun , changing API will break codes outside of this REPO if any.
It would be better to (1) add infer() (2) notify users to change codes before YY/MM (3) deprecate inference() at YY/MM.

Fortunately, there is no use case for this api. I introduced this api last week (#1574). So I think it's better to change it quickly before someone uses it. :) Thank you!!!


share a term.js ?

hello,
Is it possible to share  a terminal ?
If 2 persons have the same url for a term.js , can see and interact with the terminal at the same time ?
thanks

@dezechristophe I build a service that does that: http://share-term.me/
Sharing + Remote control :joy:


docs(how-to-guides): add example procedure, case of localization

Description
PR for https://github.com/autowarefoundation/autoware-documentation/issues/400, which add document about procedure of introducing a new node of localization.
The added pages leads to the necessary information rather than adding new information.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The Reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@mitsudome-r @kenji-miyake
Could you please review this pull request?
The content itself is briefly reviewed by @KYabuuchi once before translation.

FYI: adding the label deploy-docs will generate a documentation page, which is helpful to the review.
(I have already added it in this time.)

I will review today! I aplogize  for the delay. :bow:

@KYabuuchi
Thank you for your thorough review. I fully agree with your suggestions. All of these have been reflected.


Update Issue Template

Updates the bug.md issue template https://github.com/cyberark/conjur-template/issues/10

merging though the tests are failing, since this code change is not the cause


Receiving syntax errors when using camping

I just installed camping 3.1.3 with gem install on a version of TruffleRuby compatible with Ruby 3.2.2, and whenever I try to run any camping commands I get the following error:
<internal:core> core/kernel.rb:266:in 'gem_original_require': /root/.gem/truffleruby/<IP_ADDRESS>.1.0/gems/camping-3.1.3/lib/camping/gear/nancy.rb:68: syntax error, unexpected '=>'

Could you provide a sample app that uses the failing syntax?

@idk837384 Could you retry this on Truffle Ruby with the latest version of Camping: (3.2.4). This should be resolved. I'll also add TruffleRuby to the ruby versions we test against.


timeout waiting for response

Is this go-smpp issue or issue at the SMPP Server ?
Any message submitted to SMPP throws back "timeout waiting for response"

This issue i also observed. As per the code,callback should hit for SMPP_SM_RESP but it never hit,although all SUBMIT_SM are sent from application.
Can anyone help us for the same.

Solution is there. We had fixed it.After internal review we will update.

so when is it getting updated so that I update fetch again ?

@Munmendu any update when would it be pushed as update ?

Solution is there. We had fixed it.After internal review we will update.

Dear @Munmendu can you please provide the solution as beta solution. As this is a serious issue

@Munmendu Can we get resolution for this please ?

@fiorix
Is this 'timeout waiting for response' resolved ?

I think this is a question to @Munmendu who claims to have a solution. I have not had visibility into the problem or solution and haven't actively used this code in over 5 years now ;)

@fiorix I doubt @Munmendu has solution else he would have mentioned

@fiorix
I figured it out. In transceiver we have to set value for RespTimeout parameter
RespTimeout : 10 * time.Second
and the issue stopped completely


Password reset functionality not available?

No Admin or TeamLead reset functionality for local subordinate user. Can it be done from database?

You can do that from the rails console. Not db, since password is encrypted and stored.
user = User.find_by_email('#someemail') user.update(password: 'password', password_confirmation: 'password')

Thank you! Appreciate the feedback.


Clangd 11 RC1: Extract to function messes up namespaces and strings, doesn't work for member functions

Playing around with the "Extract to function" refactoring with clangd 11, and seeing some obvious issues.
For example, this is the code before refactoring:
#include <iostream>
#include <vector>

namespace foo {

int main() {
  std::vector<std::string> v1{"1", "2", "3", "4"};
  std::vector<std::string> v2{"a", "b", "c", "d"};

  for (auto s1 : v1) {
    for (auto s2 : v2) {
      std::cout << s1 << s2 << std::endl;
    }
  }

  return 0;
}
} // namespace foo

Now if I extract the inner loop as a function, I get the following:
void extracted(std::std::vector<std::string> &v2,
               basic_string<char, char_traits<char>, allocator<char>> &s1) {
  for (auto s2 : v2) {
    std::cout << s1 << s2 << std::endl;
  }
}

Multiple issues here:

Namespace specifier in extracted function signature becomes std::std::, which is obviously wrong
Instead of std::string, it expanded to basic_string<char, char_traits<char>, allocator<char>>, which is probably not what most people would want to use here.
Also the basic_string in 2) doesn't compile due to missing namespace specifiers, correct would be std::basic_string<char, std::char_traits<char>, std::allocator<char>>
Both v1 and s1 in extracted could be const qualified, as they are not modified by the function.
Also, does "Extract to function" only work for free functions and not member functions? Can't seem to get it to work at all when I wrap the example above in a class.

Yep, these are all valid issues. Some notes, for when we pick this up:

Instead of std::string, it expanded to basic_string<...>

Note that "string" is never spelled in the original code, so it's hard to know (in general) what type is intended. We need some heuristics here, as the AST doesn't contain links from underlying type -> alias.

Also the basic_string in 2) doesn't compile due to missing namespace specifiers

Right - this is probably as-spelled in std::vector's definition, which doesn't need the qualifiers.

Both v1 and s1 in extracted could be const qualified, as they are not modified by the function

For v2 this is only half-true: the foreach uses the non-const begin(), and in principle the const and non-const overloads could have different semantics. We need heuristics here again.

does "Extract to function" only work for free functions and not member functions

Currently, yes.

Thanks for the response Sam. Looks like this feature is still a big work in progress. Would be a very powerful tool though if this could work reliably, including support for member functions.


Expose all actuators under the CloudFoundry context

Description
Skip the exposure check when building the list of exposed actuators under /cloudfoundryapplication
Fixes #1293
Quality checklist

[ ] Your code complies with our Coding Style.
[ ] You've updated unit and/or integration tests for your change, where applicable.
[ ] You've updated documentation for your change, where applicable.
If your change affects other repositories, such as Documentation, Samples and/or MainSite, add linked PRs here.
[ ] There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.
[ ] You've added required license files and/or file headers (explaining where the code came from with proper attribution), where code is copied from StackOverflow, a blog, or OSS.

/azp run cleanup-code

While I appreciate the effort to convert xUnit assertions to FluentAssertions-style, it should be done with great care. Please carefully read https://fluentassertions.com/tips/, which lists how to write good assertions with FA. Simply converting existing assertions to FA-style syntax makes it questionable why to use the library in the first place.
When I checked a year ago, there existed two analyzers to help with the conversion and suggest better assertions. But when I tried them, they were buggy or had severe performance impact. I'd like to revisit this as part of #931.

I did try to change most/all of the assertions in a file when I ran into stupid test failure messages (false should be true, etc) so we'd at least be closer to where we want to be here, but admittedly put very little effort into true improvements... I'm sure I've read those tips before, but clearly haven't fully absorbed them, so I've bookmarked the page and will attempt to keep them in mind in the future, thanks.


Applications have same Id under Linux

The status notifier plugin on Linux (XFCE) allows you to rearrange tray icons.
When running the example app, it looks like the Id property ("1") is used in this list:

All fyne-io/systray applications use the same entry and therefore cannot be rearranged/hidden individually. This property is hardcoded here:
https://github.com/fyne-io/systray/blob/b6a2d6ca2a7be3f45d6299fa7e02311667402595/systray_unix.go#L272
Changing the code section above to,
"Id": {
	Value:    t.title,
	...
},

will use the application Title in the list:

I'm not sure if this modification violates some specifications or if the property is related to the one used in:
https://github.com/fyne-io/systray/blob/b6a2d6ca2a7be3f45d6299fa7e02311667402595/systray_unix.go#L178
If not, I would suggest this as a bug fix.

That does sound like a bug. Feel free to open a pull request. Contributions are always appreciated

Any news if #51 can be merged?

Sorry. For the delay. We've been quite busy. I don't currently have any system tray set up for testing but I'll see that it get reviewed


custom Model struct doesn't populate ID properly

What version of Go are you using (go version)?
1.10
Which database and its version are you using?
Postgres 9.4
Please provide a complete runnable program to reproduce your issue. IMPORTANT
Will provide soon. Basically, if I have
type model struct {
  ID uuid.UUID
}

type Person struct {
  model
  Name string
  Age int
}

func main() {
  ...
  p := Person{"Bob", 34}
  db.Create(&p)
  fmt.Println(p.ID)
}

the ID doesn't get set.

I have created a repo as an example of this bug: https://github.com/ags799/gorm-1950

@ags799  maybe you should use type Model struct instead of type model struct so that gorm can access the p.ID.

@zxdvd thanks this works


Cache thumbnail URLs? or re-request each time.

Sent this to David Rosen. Wait for clarification:

Hi, another API question. At http://developers.cimediacloud.com/#previews it says:

These previews are subject to changes at any time.

I'm guessing this means not just the content of the thumbnail images, but the URLs themselves? It would help us to know how volatile this data is... It would make our architecture simpler and faster if we could cache the values in our local database, rather than hitting the API every time, and simply refresh the whole cache when it gets stale... but that may not be a good call.

Thanks for any advice.

Got the report back that they thumbnail and proxy URLs should be good for a year, at least, so we'll cache them. Closed.


chore(Dockerfile): update Grafana to 4.3.2

Thanks for the contribution! Please ensure your commits follow our style guide. This code will be tested once a Deis maintainer reviews it.

cc @mboersma @vdice

I noticed this along with the older influx version being used. v1.2 brings in subqueries. Would you like me to send a PR for the same or update that?

You could just update this PR with that change too if you want.

Jenkins, OK to test

@avi-jain Thanks for the PR!  LGTM, just going to kick of CI to make sure it's happy.  I'll assume a follow-up PR for bumping influxdb will be separate...


Add ng-enter-end ng-leave-end to handle final animation states

Currently all animation helper classes (ng-enter, ng-enter-active, etc.) dissapear when the element ends the animation.
In the case you need an element hidden in its natural state but shown after the animation ends you have no way to control this but to add additional classes. This makes animation classes less reusable as you depend on the controller or custom directives to control final animation state.
Adding and keeping ng-enter-end, ng-leave-end or similar only when present in the css should do the trick.
This or another way where you can define inverse animations (in which the final state is the actual state you want) should be present.

@rlucha could you please provide an example on plnkr or jsbin?

I'm going to close this issue because we haven't got any feedback. Feel free to reopen this issue if you can provide new feedback.


[Bug] Updating from 0.34.1 to 0.36.1 yields missing symbols with dev middleware

Reproducible in vscode.dev or in VS Code Desktop?

[X] Not reproducible in vscode.dev or VS Code Desktop

Reproducible in the monaco editor playground?

[X] Not reproducible in the monaco editor playground

Monaco Editor Playground Link
No response
Monaco Editor Playground Code
No response
Reproduction Steps
This might be something specific to my project, but cloning git@github.com:compiler-explorer/compiler-explorer.git and then checking out mg/monaco_36 branch - make dev shows up the problems
Module not found: Error: Can't resolve './contrib/stickyScroll/browser/stickyScroll.js' in '/home/matthew/dev/ce/compiler-explorer/node_modules/monaco-editor/esm/vs/editor'
Module not found: Error: Can't resolve './contrib/viewportSemanticTokens/browser/viewportSemanticTokens.js' in '/home/matthew/dev/ce/compiler-explorer/node_modules/monaco-editor/esm/vs/editor'

both seem internal to monaco.
Interestingly a npm run webpack doesn't show up the problem: it seems to be only when I use the dev middleware
Actual (Problematic) Behavior
My project has used Monaco for years. I just went to update it from 0.34.1 to 0.36.1 and during webpacking there appear to be missing symbols:
ERROR in ./node_modules/monaco-editor/esm/vs/editor/editor.api.js 76:0-57
Module not found: Error: Can't resolve './contrib/stickyScroll/browser/stickyScroll.js' in '/home/matthew/dev/ce/compiler-explorer/node_modules/monaco-editor/esm/vs/editor'
 @ ./static/themes.ts 29:22-46
 @ ./static/main.ts 47:34-56

ERROR in ./node_modules/monaco-editor/esm/vs/editor/editor.api.js 84:0-77
Module not found: Error: Can't resolve './contrib/viewportSemanticTokens/browser/viewportSemanticTokens.js' in '/home/matthew/dev/ce/compiler-explorer/node_modules/monaco-editor/esm/vs/editor'
 @ ./static/themes.ts 29:22-46
 @ ./static/main.ts 47:34-56

Expected Behavior
All symbols to be found
Additional Context
I can easily believe this is something unusual in my setup. However, we've not had issues of this form before with Monaco, so I was hoping by filing this someone might recognise the issue and offer aid, if it's not an issue in monaco's webpack support itself.
From the release notes the sticky scroll seems to be a new feature.

This was - as all good problems are - a broken cache in our webpack setup. Sorry for the noise.


[#180081291] stop removing envvar

What

Revert "REMOVEME: remove vestigial envar"

This was just to ensure an old envvar was removed on the first deployment. It is now not needed, as it has been run once.
How to review

Code review

🚨⚠ Please do not merge this pull request via the GitHub UI ⚠🚨

Can you explain like I'm 5?
I got confused about whether or not I need to remove a commit, and to me it looks as if these are the same changes as in #2776
Do I just need more ☕

Can you explain like I'm 5? I got confused about whether or not I need to remove a commit, and to me it looks as if these are the same changes as in #2776 Do I just need more coffee

😂 no, I think I'm bad at describing!
So, the first one needs to be merged first. once it's merged, this one will look more sensible, as the Update Aiven Broker deployment for OpenSearch commit will drop off, and it'll just be the revert commit in the changeset. does that make more sense? ☕

Can you explain like I'm 5? I got confused about whether or not I need to remove a commit, and to me it looks as if these are the same changes as in #2776 Do I just need more coffee

😂 no, I think I'm bad at describing!
So, the first one needs to be merged first. once it's merged, this one will look more sensible, as the Update Aiven Broker deployment for OpenSearch commit will drop off, and it'll just be the revert commit in the changeset. does that make more sense? ☕

What you're saying makes sense, that's what I thought would happen. But I'm seeing the same commits in both PRs, and suddenly things don't have sense anymore 😭

What you're saying makes sense, that's what I thought would happen. But I'm seeing the same commits in both PRs, and suddenly things don't have sense anymore sob

So, I've just branched from my original branch, so all the commits are there. as it's a revert it's easier to see what'll happen if the commit that's being reverted is also in this branch. I think it'll all make sense after the other PR is merged. maybe.


Code execution 8x slower using sneakers

Greetings!
First off, let me thank you for maintaining this great project! We're using sneakers in several apps without any trouble and we're loving it.
However, we recently stumbled upon a very strange case. We wanted to extract a background worker from a rails monolith into a separate service. We therefore switched from using Que to sneakers as a first step. We then noticed a performance degradation in the execution time of our background jobs by a factor of ~8.
This background process is very CPU intensive (5-30 seconds of 100% CPU usage, after switching to sneakers 8 times that).
While we do have some suspicions, we are unable to pin down the root cause. However, I have been able to come up with a simple example that shows similar characteristics. Just have a worker compute the following:
100_000.times { Time.parse(Time.utc(2016).iso8601) }

Using Ruby 2.3.1 this takes 3.5 seconds on my machine without using sneakers and 19 seconds using sneakers. I realise it is unfair to compare using sneakers against leaving it out but I guess we can all agree that 16 seconds overhead isn't what any of us would expect.
If you are able to reproduce this, do you have any idea what may cause this?
Best regards,
Kai

Same problem here, performance degrades significantly when using sneakers.

could be due to multiple context switch (threads)?
try reducing the amount of threads and scaling with process only.
CPU intensive tasks get a lot of penalty with threads (because of the GIL).

If I remember correctly we configured sneakers to spawn one worker per CPU.
I've created a small example to reproduce this issue https://github.com/kaikuchn/sneakers-issue-231 just clone and run it.

It seems to be related to the behavior of Process.fork on OS X. See http://stackoverflow.com/questions/38844392/why-does-process-fork-make-stuff-slower-in-ruby-on-os-x.

Confirmed, this is an issue with OS X. But I guess pretty much about nobody uses that in production anyway so.. I'm closing this.


UV on gitlab CICD has some issue

I am not sure at the moment, if this is an issue with the uv image or a bug on gitlab, but I stumbled over a different issue when testing my pipelines:
I have tested the following scenarios with different small changes based on the presented errors:
Gitlab runner on Kubernetes executor:
.gitlab-ci.yml:
variables:
  UV_VERSION: 0.5
  PYTHON_VERSION: 3.12
  BASE_LAYER: bookworm-slim

test_ndp_cli:
  stage: test
  image: ghcr.io/astral-sh/uv:latest
  variables:
    UV_CACHE_DIR: .uv-cache
  cache:
    - key:
        files:
          - uv.lock
      paths:
        - $UV_CACHE_DIR
  script:
    - uv python install
    - uv sync --all-extras --dev
    - uv run pytest
    - uv cache prune --ci

result:
ERROR: Job failed (system failure): prepare environment: setting up trapping scripts on emptyDir: unable to upgrade connection: container not found ("build"). Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information

I have diagnosed a few issues with our kubernetes system, so I have run it multiple times and got a different result:
WARNING: Event retrieved from the cluster: Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown
ERROR: Job failed (system failure): prepare environment: waiting for pod running: timed out waiting for pod to start. Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information

So I thought maybe still something wrong on Kubernetes, let me test on a standalone-docker executor:
result:
Using docker image sha256:b4f508bf6cb1eda0e534b608a2a4dec80a8d01cfa2c4f3f8953537b60734d729 for ghcr.io/astral-sh/uv:latest with digest ghcr.io/astral-sh/uv@sha256:5436c72d52c9c0d011010ce68f4c399702b3b0764adcf282fe0e546f20ebaef6 ...
error: unrecognized subcommand 'sh'
Usage: uv [OPTIONS] <COMMAND>
For more information, try '--help'.
Cleaning up project directory and file based variables 00:01
ERROR: Job failed: exit code 2

Something again with 'sh' so I thought lets test with empty entrypoint:
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 909efe2..f30df03 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -16,8 +16,12 @@ variables:
   BASE_LAYER: bookworm-slim

 test_ndp_cli:
+  tags: [docker-standalone]
+
   stage: test
-  image: ghcr.io/astral-sh/uv:latest
+  image:
+    name: ghcr.io/astral-sh/uv:latest
+    entrypoint: [""]
   variables:
     UV_CACHE_DIR: .uv-cache
   cache:
@@ -33,8 +37,11 @@ test_ndp_cli:
     - uv cache prune --ci

 build_linux:
+  tags: [docker-standalone]
   stage: build
-  image: ghcr.io/astral-sh/uv:latest
+  image:
+    name: ghcr.io/astral-sh/uv:latest
+    entrypoint: [""]
   variables:
     UV_CACHE_DIR: .uv-cache
   cache:

result:
ERROR: Job failed (system failure): Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown (exec.go:77:0s)

Have you tried using an image as described in our GitLab integration guide? https://docs.astral.sh/uv/guides/integration/gitlab/
For GitLab, you'll want an image that isn't distroless: https://docs.astral.sh/uv/guides/integration/docker/#available-images

I was blind and deaf the hole time. As you can see I already had the variables ready but for what ever reason I missed entering the image correctly.
I always tinker at the wrong position... Thanks for pointing out. Kube now works as expected...


Fix: Move from optparse to argsparse

Move to argsparse. Closes #10.

This fork is the only one that easily works for me :D

Sweet, thanks! I've just merged #12 which fixes the same issue.


[For discussion] Experiment with Calendar Integration

Moving towards indicating intention to attend a conference.
Just a draft for now, with some hacks to resolve.

Nice idea!

@joreilly OK, I'll clean it up.
This is the no permission, launch an intent.
We can also use the commented out API behind permissions checks.


Tidy up testdata

@drott suggested:

Similar to practices in Chromium or our other open source projects, I would suggest to create a test_data/third_party/ or test_data/third_party/harfbuzz directory, and please a readme with provenance and license there, so we have a clear indication where the font is coming from.

The original comment was for one specific test file but I think it applies to all our test data.

@drott do you think this is required for Chrome launch? - waffled over whether to mark that milestone.

do you think this is required for Chrome launch?

No, but should happen rather sooner than later, as it becomes more difficult to figure out what came from where over time.


Edison: try / catch not supported

The following program EdisonExceptionTest.xml.txt cannot be tranferred to edison, the reason is the not supported try / catch statement:

Maybe there is an option to work with newer/better firmware, this should be checked before trying to solve this bug. The solution might not be easy to implement.
I checked one of our edison yesterday, there is no update for the firmware available (@bjost2s ), so:
A quick workaround would be to simply remove "break" and "continue" from the toolboxes.

fixed in 081d23be14c9fdee9947640c4626de0b657b132a, together with #1446

Tested successfully on test server. Toolbox does not contain break out/continue with next iteration block for Edison.


消息相关事件不支持

使用自带的SampleHandler类测试，消息相关事件钩子初始化报warning，且不被调用。
Starting emqx on node<EMAIL_ADDRESS>Start http:management listener on 8081 successfully. Start http:dashboard listener on 18083 successfully. 2020-06-08 14:23:20.032 [warning] [ExHook Driver] Unsupprorted hook type message_dropped, module: SampleHandler, func: onMessageDroppedRaw 2020-06-08 14:23:20.032 [warning] [ExHook Driver] Unsupprorted hook type message_acked, module: SampleHandler, func: onMessageAckedRaw 2020-06-08 14:23:20.032 [warning] [ExHook Driver] Unsupprorted hook type message_delivered, module: SampleHandler, func: onMessageDeliveredRaw 2020-06-08 14:23:20.033 [warning] [ExHook Driver] Unsupprorted hook type message_publish, module: SampleHandler, func: onMessagePublishRaw Start mqtt:tcp listener on <IP_ADDRESS>:11883 successfully. Start mqtt:tcp listener on <IP_ADDRESS>:1883 successfully. Start mqtt:ws listener on <IP_ADDRESS>:8083 successfully. Start mqtt:ssl listener on <IP_ADDRESS>:8883 successfully. Start mqtt:wss listener on <IP_ADDRESS>:8084 successfully. EMQ X Broker 4.1.0 is running now! Eshell V10.7  (abort with ^G)

Sorry @gzywalker. All message.* hook provided on Enterprise version only

OK, I see..


fix(ui): make version copyable from info box

Fixes #916

Pull Request Test Coverage Report for Build 675586312

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 18.209%

Totals

Change from base Build 675537053:
0.0%

Covered Lines:
2026

Relevant Lines:
11410

💛  - Coveralls


Deprecating long-lived credentials for container repositories for terraform-template-poc

Background

To improve the security of services running on the Cloud Platform, we are removing the ability to create and use long-lived credentials, such as IAM access keys, from our modules. These are being replaced by short-lived credentials.
For container repositories, this means utilising native OpenID Connect implementations for GitHub Actions and CircleCI.
You should start using short-lived credentials as soon as you can. Long-lived credentials will be entirely removed from the container repository on Monday, 4th September 2023.

Instructions
https://user-guide.cloud-platform.service.justice.gov.uk/documentation/deploying-an-app/container-repositories/deprecating-long-lived-credentials.html#deprecating-long-lived-credentials-for-container-repositories
Acceptance Criteria:
No longer using long lived creds for container repositories
Assumption
Some refactoring of apps may be required in support of this change.
Notes:
Cloud Platform Comms
Guidance/Instructions

Can this ticket be closed as a duplicate?

https://user-guide.cloud-platform.service.justice.gov.uk/documentation/deploying-an-app/container-repositories/deprecating-long-lived-credentials.html#migrating-to-short-lived-credentials-for-github-actions

This ticket involves updating the GH actions to use the AWS credentials in the above link in the following repos:
terraform-template-poc repo: merge-into-main.yml

Use the GH Action secret that contains the Role ARN which be applied to the operations-engineering CP Namespace in ticket #3243. This role will allow access to S3 and DynamoDB

Example of what need to achieve between CP and GH Action

In .yml files need to use something along the lines of
    - name: Configure AWS Credentials
      uses: aws-actions/configure-aws-credentials@v2
      with:
        aws-region:  {{ secrets.CP_REGION }}
        role-to-assume: {{ secrets.AWS_ROLE }}
        role-session-name: ?

Where AWS_ROLE is the Kube secret that looks like arn:aws:iam::123456789100:role/my-github-actions-role
Not sure what "role-session-name" should be.

Closing due to no work needed - currently we are creating the user within the terraform-template-poc-state.tf and are not using any of the long lived credentials (defined in the CP modules) due for deprecation.


App starts at MIN_SIZE instead of PREF_SIZE when jar is launched

860 x 600px instead of
1280 x 720px

Might be because of GuiSettings.java.


sudo staartxfce4 has error (EE) The '-logfile' option cannot be used with elevated privileges.

when i try to sudo startxfce4 this happens

after that it just dosn't do anything dosn't quit untill I crtl c

Same thing for me.  It is a kali linux chroot that was working until I updated packages.

I did find that if i edited this file: /etc/crouton/xserverrc-xiwi
And commented this line: #XARGS="-nolisten tcp -config xorg-dummy.conf -logfile $logfile"
And added this: XARGS="-nolisten tcp -config xorg-dummy.conf"
X11 would start.  Not sure the remifications of turning off logging like this, though.

That happens to me also, but I only get 2 (EE)

I have the same problem. Is there a solution?
/etc/crouton/xserverrc-xiwi   the file does not exist.
I am confused.

also affects me on xenial after some ubuntu OS updates.

#2875


Replace all %s with .format; break up dense lines

All uses of %s and %d have been replaced with .format. API paths always use keywords, but miscellaneous messages are just fine with the {0} style.
Unfortunately, this made a lot of places feel cramped, especially the mixin methods. I decided to move a lot of the URL formatting onto their own lines instead of trying to keep a hole-in-one. 79 characters is too small for most of these :frowning:
For two of the API paths, I had to break them into separate lines and get some parentheses involved. It looks a little funky, but it was the only way to stop flake8 from complaining about my visual indent without putting the continuation line too far to the left.
Please review thoroughly if you can. After staring at the word "format" for so long it's hard to proofread this myself.
Thanks!

Edit: Woah, what happened to Travis? All tests are passing for me locally. Is the CI suite using some new parameters that make the requests not match?

@voussoir have you updated the coverage module locally m a similar error occurred with the 3.2 stuff when coverage updated, so it looks like it did again. If  updating the coverage module via pip breaks tests, then the betamax decorator needs to be updated / get Travis to use an older version.

Darn, you're right. I just upgraded betamax and everything broke. Rather than downgrading Travis' version, I'll see if I can fix the problems. Most of the cassettes probably just need to be regenerated, there's only a few that had actual assertion errors. That will be my project this weekend then, thanks for the tip!

Good luck! The last time I tried to check tests I failed miserably.
Speaking of which, one of the tests actually has to be changed, since reddit's API actually changed at some point (one of the things is no longer equal to None, but rather an empty list. Don't remember what though. Something with inbox comments.)

These changes look great. My only suggestion would be to not roll any cassette changes into the same pull request. If you depend on the cassettes being fixed first, that should be done separately so that this PR doesn't require any cassette updates.

@13steinj Yeah, it looks like this is a good opportunity to go double-check that all the tests actually work and fix the ones like you mentioned. I wasn't expecting to have to deal with this, but it's a good excuse to go freshen some things up.
@bboe Thanks Bryce, I will definitely create a new PR for the cassettes, there will be lots of them. This PR doesn't rely on the tests passing since no API or user interaction changes were made, so we can merge it now unless you would prefer not to have PRAW in a state of CI failure. I don't mind letting this one sit for a while until the tests are fixed, it's not super important. Up to you!

@voussoir It's possible that if you did make a mistake that many of the tests would fail. Hence I would suggest holding off until the tests are passing before merging this PR in.
Another reason to wait is that these sort of changes should have no impact on a test, so we can verify that by seeing all existing set of tests pass without requiring modification. That's one of the most important reasons for having them.

@voussoir It seeems that the test suite fixed itself, so try git rebase -i master and then git push --force just to make Travis run again. If it works, then there was some weird temporary glitch. If it doesn't, you made an error somewhere (but I'm too  blind to see where exactly, sorry.).

Oh man, I feel terrible, I had completely forgotten about this PR. Just rebased and pushed, tests are currently running and looking good so far. Sorry for dropping the ball here everybody.

@voussoir Eh, probably no biggy. Probably for the best given if you did attempt to fix it it would be for nothing, since it was in fact some weird temporary glitch (I'm assuming betamax had a faulty release). :P Don't know why the coverage went down though.

Merged. The coverage went down because more lines were added which is expected due to the increase in line lengths. Thanks @voussoir.


some ToDo s to make things better

add a ToDo proposal avoid recompiling regex (twice!) on every use
add a ToDo proposal to save a lot (?) of memory
remove some trailing blanks

Feel free to add a commit about a compiled constant regex. I don't have an opinion on the other topic.

Nice find.
For the flag thing, how about just changing isValid to this?
    public boolean isValid()
    {
        return value != Long.MAX_VALUE && value != Long.MIN_VALUE;
    }

This would also make the constructor and where it is called a little bit shorter because there'd be no need to pass the validparameter.
And the STATIC array could just be initialised in a static block, IMHO that wouldn't cost too much memory, and get(long) would be much simpler:
    public static COSInteger get(long val)
    {
        if (LOW <= val && val <= HIGH)
        {
            return STATIC[(int) val - LOW];
        }
        return new COSInteger(val, true);
    }

getInvalid(boolean maxValue) can also be removed and we use just
    protected static final COSInteger OUT_OF_RANGE_MAX = getInvalid(Long.MAX_VALUE);
    protected static final COSInteger OUT_OF_RANGE_MIN = getInvalid(Long.MIN_VALUE);

@THausherr What do you think about the suggested change? I just "bought" the PDF spec yesterday (you have to buy it, but the price is 0 USD), and I couldn't find anything about COInteger to require Long.MIN_VALUE and Long.MAX_VALUE to map to valid COSInteger values.
@DvonHolten if Tilman and/or some other maintainer agrees to the proposed change, do you want to make the flag related change yourself or should I create a PR for that?

I'm not deep enough into the COSInteger code, it is related to PDFBOX-5176 and any change (except removing getInvalid() because of https://twitter.com/unclebobmartin/status/1114137614377005057 ) should be checked with the file from there and with the file from the earlier issue. PDFBOX-5176 was created after running a regression test on 250000 PDF files.

i can do it - check, where the invalid things are coming from and where they are checked. if all the Long-values must be available, a subclass may do it.
and i have a closer look at those 250000 pdf -files in PDFBOX-5176. i assume, they are just created to check the parser - not to render them?

You don't have to bother with the 250000 files, this is our regression test corpus and we run these once on a dedicated server before doing a release. Just test the files from PDFBOX-5176 and the one from the related issue. I mentioned the 250000 files to show how unlikely this is.

I've now committed the javadoc changes and the pattern change.


Move setup documentation to the wiki

README.md is way too long. Move content over to the wiki in preparation for also explaining how to set up Blue Iris.

 Will likely just start with a wiki and images checked into docs/

Will need to eventually use pages, the wiki is just too limiting in terms of page structure.


Aliyun API InvalidParameter error

When I tried to expose a test Nginx svc with a loadbalancer, an error occures in the controller manager.
E0814 00:16:35.074058   11287 service_controller.go:1123] Failed to process service default/nginx. Retrying in 10s: failed to ensure load balancer for service default/nginx: Aliyun API Error: RequestId: 2FB40702-3271-4C27-8564-2B9E9BFF2F3D Status Code: 400 Code: InvalidParameter Message: The specified HealthCheckType is invalid.

what is your configuration? Thanks

Fix in https://github.com/AliyunContainerService/alicloud-controller-manager/pull/12/files .

No special configuration.
#12  fixed the issue. Just confirmed.


Broken link to contracts config

The provided link to the contracts pallet config reference is broken, this should fix it.

Hi @rvalle - thanks for helping fix this ! I'm about to merge a PR (#1128) that has this change already. Cheers.


Create a Module System for Loading Source Code into the Browser for DEV

Consider using systemjs to load files into the browser when testing. This could save us from tediously having to add the src script files one-by-one.
For production deployment, we can concatenate the modules together with something like systemjs builder, because our dist still needs to be a single ES5 file.
The problem I see with this, which hopefully is trivial to resolve: how do we load 3rd party libraries through systemjs. Can we leverage it in phantomjs for testing with karma as well?

jspm with systemjs seems to be the way to go. Only concern is if any library is possibly not supported through jspm

@arjshiv and I discussed, we will use webpack to create a deployable distribution and use jspm for DEV dependency management. we will export the Grid itself and I will write a d.ts file to target TypeScript audience

@arjshiv I got webpack working by targeting libraryTarget: "umd" and explicitly naming react as the dependency of the bundle (and specifying its name for each module system that might load it).
On the other hand, to get modules like jquert flux to bundle, I installed them under node_modules instead of jspm_modules this means we are handling two sets of dependencies in the same package.json, I suspect we can write a easy plugin in webpack.config.js to eliminate the need to double track dependencies.

@arjshiv should we declare victory at this? we still technically can't bundle font-awesome and I have not fully tested this for global ...


feat(platform_wrapper): add web support Platform -> TargetPlatform

Codecov Report

Merging #24 (728fb68) into main (f83c222) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #24   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         7
  Lines          178       178
=========================================
  Hits           178       178

Impacted Files
Coverage Δ

lib/utills/platform_wrapper.dart
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


train？

Hello, I'm new to this field. Does your code only have inference? Is there any training code?

Hi, this method does not require training. It uses a pre-trained model from segcontrast and creates a graph from the point cloud, using the point-wise features from the model to define the graph edge weights. To train this pre-trained model, all the instructions are available on the segcontrast [repo(https://github.com/PRBonn/segcontrast).