Elm 0.19, OS X/Ubuntu: Compiler crashes with "not enough bytes", on large project after 1) failed build, 2) trying to build again

Affects OS X and Linux consistently.

Elm 0.19
OS X Mojave
Ubuntu 18.04

Steps to reproduce:

Create a large project.
Introduce a build-failing error into the code.
Compile the first time.
Compile a second time.

Workaround:
Delete "elm-stuff" and try again.
Example output:
make MyProject.js
elm make  src/MyProject.elm --output ./release/MyProject.js
Dependencies loaded from local cache.
Dependencies ready!
Detected errors in 1 module.
-- TYPE MISMATCH --------------------------------------- src/MyProject.elm

The 1st argument to `initWithFlags` is not what I expect:
# [...]

# Try again!
elm make  src/MyProject.elm --output ./release/MyProject.js
elm: not enough bytes
CallStack (from HasCallStack):
  error, called at libraries/binary/src/Data/Binary.hs:212:21 in binary-<IP_ADDRESS>:Data.Binary
make[1]: *** [MyProject.js] Error 1
make: *** [test] Error 2

Comments
I have noticed that it seems to occur more often if the original compiler error is very "deep" in the app. I have a very complicated widget that I re-use repeatedly very deep in most of my views, and introducing an error into it almost always causes this bug.
This is really messing up my workflow, because the workaround makes builds take much longer. I have several codebases that have grown to be affected by this bug. The main issue with submitting a quality bug report is that all my affected code is proprietary, so I fully understand if you want to moderate this away as a "low quality" bug report. I would love to send the maintainers my codebase, I just can't post it on github.
Thanks!

I see this constantly too, unpredictably in a large Elm codebase with several errors present: I'm working on upgrading from 0.18 to 0.19. Haven't figured out a pattern yet.

I'm seeing this too, more often now that a project I'm working on is growing really big.
I'm using Ubuntu (with Docker over macOS) and a file watcher to recompile whenever any file changes. The error appears randomly, sometimes when I change a bunch of files at the same time, sometimes when I change a single file.
The workaround is indeed removing elm-stuff.

Since the problem for us seems to occur from having only a .elmi file without a matching .elmo one we run a script to ensure consistency between .elmi and .elmo files before running elm make.
So in our gulpfile.js we have a task that runs the function below before doing elm make or elm bundle.
return function() {
    var elmStuff = src + "elm-stuff";
    function checkFiles(fileToCheck, matchingFileType) {
        var files = glob.sync(elmStuff + "/**/*." + fileToCheck, {});

        for (var i = 0; i < files.length; i++) {
            var file = files[i];
            var matchingFile = file.replace(/\.[^/.]+$/, "") + "." + matchingFileType;

            if(fs.existsSync(file) && !fs.existsSync(matchingFile)) {
                console.error('Found ' + file + ' but not expected matching file ' + matchingFile);
                rimraf.sync(file);
            }
        }
    }

    checkFiles('elmi', 'elmo');
    checkFiles('elmo', 'elmi');
};

The script just goes through the elm-stuff directory and checks for all .elmi files if there is no matching .elmo one, if so it removes the .elmi file and then vice versa for all .elmo files. This does means the entire elm-stuff directory doesn't have to rebuilt at least.

For people seeing this issue, are you using an editor that is running elm make automatically? Is it possible that this happens when there are two concurrent elm make commands issued?

I wish, but I have a repo that it happens on without any editor open 100% of the time.

@evancz
I am using webpack with a elm-loader and normal settings. I have even tried to run webpack's elm make command from terminal. Same thing.

@evancz
You actually may have a point, I can confirm that triggering many compilation events causes two types of errors:

The binary data at /project/elm-stuff/0.19.0/name-of-file.elmo is corrupt. Removing this file solves the problem.

elm: not enough bytes. The problem described in this issue.

The events were fired by saving a file several times in a row (3-4 usually). I used a file that is imported by many other modules, so the compilation takes a little longer. At least one of the errors happen every time after the third or fourth compilation.
I use a file watcher (chokidar-cli) that triggers elm make if a file changes. The tool has --debounce and --throttle parameters, but I use with the default values, that are 400 and 0 respectively.

I've been playing with a simple temporary solution that apparently works in my particular case. Instead of running elm make directly, the file watcher runs this script:
if [[ -a .compiling ]]; then
    echo "Still compiling..."
else
    touch .compiling
    elm make src/Main.elm --output /path/to/public/elm.js
    rm .compiling
fi

This works because elm-make blocks, and rm .compiling is not executed until it finishes.
Maybe the solution is as simple as saving some flag (like a temporary file or something smarter and more efficient) and then blocking any subsequent compilation until the current one finishes.

@evancz I can reproduce the error by removing elm-stuff (to ensure all modules have to be rebuilt), editing a file to make it produce an error, running elm make src/**/*.elm (which will fail to compile due to the error) and then elm make src/**/*.elm again which will print the elm: not enough bytes error.
So in our case the problem doesn't seem to be related to having concurrent elm make commands. Looking at the files it seems as if it might be that the compiler encounters the error and then finishes in a half-completed state leaving an .elmi file that isn't fully built and no matching .elmo file at all.

As @mbark describes above the problem happens when invoking a simple elm make command twice. An interesting observation however is that the size of the .elmi file does vary between runs:
-rw-rw-r--. 1 martenb martenb 953846 Nov 19 09:52 elm-stuff/0.19.0/Widget-RecTable.elmi
-rw-rw-r--. 1 martenb martenb 1084847 Nov 19 09:51 elm-stuff/0.19.0/Widget-RecTable.elmi
-rw-rw-r--. 1 martenb martenb 691839 Nov 19 09:52 elm-stuff/0.19.0/Widget-RecTable.elmi
This indicates a concurrency issue so i did a strace and saw the following:

The compiler seems to compile things in parallel (at the very least it is writing the .elmi in parallel)
The compiler keeps writing to the broken elmi file even when it start printing the compilation error.
The compiler exits when it has finished printing the compilation error, it keeps writing to the elmi file until this point but it never calls close on it.
Printing the compilation error is a relatively slow operation

In other words it seems that to trigger this issue you need to have a very big file (that compiles fine) which the compiler is not able to finish writing during the time it is printing the compilation error. This would explain why only large projects are affected.

Having the same issue on a medium-sized project
elm make src/Main.elm --output build/app.js
elm: not enough bytes
CallStack (from HasCallStack):
  error, called at src/Data/Binary.hs:212:21 in binary-<IP_ADDRESS>-1SWOkUSZj1B1k0FQ5fyFqI:Data.Binary
make: *** [Makefile:3: default] Error 1

The problem happens on one of my computers but not on the other, which seems consistent with @martenbr 's explanation.

Interesting, will the issue go away if restrict the number of available cores to the elm compiler process?

Started to get this too, I'm using Elmjutsu on Atom. So far removing elm-stuff/ works.

Interestingly enough, a VSCode user has found that disabling live linting made the issue going away:

I wonder if this issue in Elmjutsu has the same root cause, and if so what could be achieved to prevent it to happen.

I had the same issue when my elm projects were on an external hard drive. Working locally fixed it.
It is a bit annoying though since I'm working on hundreds of projects at the same time.

@wmakley, does this problem persist with 0.19.1?

It looks like a bunch of different issues have been reported in this thread.
The issues related to running elm make multiple times at once on the same project should be resolved by 0.19.1. I think the scenario explained by @martenbr can still happen though. I am going to start a new issue that specifically highlights that possibility.
If particular individuals are still seeing this kind of thing with 0.19.1, please open an issue of your own. Do not add on to an existing issue. Please share as much information about your development environment as possible. Editor? File watcher? OS? Etc.

@wmakley, does this problem persist with 0.19.1?

Nope! Miraculously I found my old repo+tag and it still had the same issue in 0.19. Then I installed 0.19 and ran into many new compiler errors and tried to work through some of them and run make multiple times, but did not encounter this issue again.

I'm having issues with running Elm v0.19.1 in parallel via lerna + webpack in certain environments. We moved to running in sequence to resolve our build issue in Heroku (although it seems to be fine locally on everyone's laptops).

@toastal, can you open a new issue with an SSCCE so we can reproduce and fix if the root problem is in the elm binary?


Buffer Accounting

Buffer Accounting: Account for allocated bytes in buffers charging to a particular downstream.
Description:
Buffer limits for Envoy are too soft. This can lead to excessive buffering, potentially OOMing Envoy. The existing mechanism which we have don't allow us to quickly close streams for existing connections to reclaim resources if we're facing memory pressure.
If we tracked how much allocated bytes in buffers a stream uses, then we would be able to create an overload manager action to help shed expensive streams when under memory pressure.
More details in the design doc.
Hope this makes sense. Thanks!

/assign @KBaichoo


Enhances from my working version.

handle having scorm source away from content.
update scorm disk with log try catch exception message

Hi @KhaledLela,
Your contribution is highly appreciated. I've gone through your code at commit [f3da307](https://github.com/devianl2/laravel-scorm/pull/21/commits/04fc94e0157136e6ce04c3d20edbf2845c4e0ebe), do you think is essential to store CMI data in createScoTracking() function?
My concern is the user has the flexibility to update their profile information in their own LMS. At the moment I generate CMI data from application controller instead of package itself so that programmer has more control over CMI data customization. What do you think?


First interaction os [BUG]

Describe the bug
The GitHub workflow first interaction uses features that are only supported on Linux but it's currently running on Windows. This is the error "Container action is only supported on Linux."
To Reproduce
Steps to reproduce the behavior:

Create an issue or merge/commit to the main or dev branch.
See error.

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
No screenshots.
Environment (please complete the following information):
GitHub workflows.
Additional context
No additional information.

This bug should be fixed now but more testing needs to be done before we can close this issue. To test that it works commit or send a pull request to the dev branch and see if the "First Interaction Greeting" workflow fails.

After thorough testing, this bug seems to be fixed and therefore I will close this issue. If a new problem appears related to this issue don't hesitate to refer to this issue.


[CI/Infra] E2E tests on Argo Workflows

Description
We've identified a need in argo workflow to allow to run e2e jobs in cluster, but as a part of GitHub CI jobs.
Issue
Fixes #718
Type of change
Please mark the relevant option(s):

[ ] New feature, functionality or library
[ ] Bug fix
[ ] Code health or cleanup
[ ] Major breaking change
[ ] Documentation
[x] Infrastructure
[x] CI/CD

List of changes

[x] E2E tests to ensure the version of containers they run against prior to executing the test (done in protocol-infra repo)
[x] Cluster manager cleans up the Pods managed by StatefulSets, if Pods are unhealthy and there is a new-er version of the software present.
[x] Dedicated CI job to run E2E tests. That allows us to start the test from the GitHub UI, no need to push the new commit.

Testing

[x] make develop_test; if any code changes were made
[ ] Docker Compose LocalNet; if any major functionality was changed or introduced
[x] k8s LocalNet; if any infrastructure
or configuration changes were made
[x] Remote DevNets

Required Checklist

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added, or updated, godoc format comments on touched members (see: tip.golang.org/doc/comment)
[ ] I have tested my changes using the available tooling
[ ] I have updated the corresponding CHANGELOG

If Applicable Checklist

[ ] I have updated the corresponding README(s); local and/or global
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added, or updated, mermaid.js diagrams in the corresponding README(s)
[ ] I have added, or updated, documentation and mermaid.js diagrams in shared/docs/* if I updated shared/*README(s)

Reminder to Monday self: add more debug output to the new cluster-manager code to troubleshoot why it might not discover pods to kill.

Reminder to Monday self: add more debug output to the new cluster-manager code to troubleshoot why it might not discover pods to kill.

I made that cluster-manager only kills pods that have cluster-manager-delete-on-crash-container annotation set, but I did not set it on DevNets. Once I added the annotation, old/crashed pods got cleaned up and DevNet became healthy! :)

The PR is ready for review. Please note, the infrastructure for this has been set up in protocol-infra repo.
You are not going to see the separate CI job until the yaml definition merged and new GitHub workflow appears in the main branch.
I did test this to the best of my ability, specifically:

as a part of an existing job - https://github.com/pokt-network/pocket/actions/runs/4963496465/jobs/8882923872
manually triggering the same commands from my machine

However, I cannot guarantee that this will work immediately, and adjustments may be required in subsequent PRs.

@Olshansk I appreciate the feedback, the code is more readable now. I kept all comments related to rangeValCopy gocritic check open in case you'll want me to change the code in these places.


PR for RAVS 305 automated test scripts update

Description
This pull request is for updating automated tests with legal mechanism changes and removing prescribing methods, also fixed some Ids in batch management screen

Mainly changes to Ids and added new pages and replaced prescribing methods models with legal mechanism models

These are automated tests updated as UI changed

[x] Refactoring (non-breaking change)
[x] New feature (non-breaking change which adds functionality)

Checklist

[x] I am familiar with the contributing guidelines
[x] I have followed the code style of the project
[x] I have added tests to cover my changes
[x] I have updated the documentation accordingly
[x] This PR is a result of pair or mob programming

Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

[x] I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

Merged and no issues.


[SPARK-47119][BUILD] Add hive-jackson-provided profile

What changes were proposed in this pull request?
This PR aims to provide a new profile, hive-jackson-provided, for Apache Spark 4.0.0.
Why are the changes needed?
Since Apache Hadoop 3.3.5, only Apache Hive requires old CodeHaus Jackson dependencies.
Apache Spark 3.5.0 tried to eliminate them completely but it's reverted due to Hive UDF support.

#40893
#42446

To allow Apache Spark 4.0 users

To provide their own CodeHaus Jackson libraries
To exclude them completely if they don't use Hive UDF.

Does this PR introduce any user-facing change?
No, this is a new profile.
How was this patch tested?
Pass the CIs and manual build.
Without hive-jackson-provided
$ dev/make-distribution.sh -Phive,hive-thriftserver
$ ls -al dist/jars/*asl*
-rw-r--r--  1 dongjoon  staff  232248 Feb 21 10:53 dist.org/jars/jackson-core-asl-1.9.13.jar
-rw-r--r--  1 dongjoon  staff  780664 Feb 21 10:53 dist.org/jars/jackson-mapper-asl-1.9.13.jar

With hive-jackson-provided
$ dev/make-distribution.sh -Phive,hive-thriftserver,hive-jackson-provided
$ ls -al dist/jars/*asl*
zsh: no matches found: dist/jars/*asl*

Was this patch authored or co-authored using generative AI tooling?
No.

I may not have enought context. The existing hive-provided seems to be changed to expect Jackson dependencies to be present in the runtime. Is that expected?

Thank you for review. This PR is for the users who keep Hive and exclude CodeHaus Jackson only. For example, a user who can use Spark Thrift Server without Hive UDFs, @xinrong-meng .

I may not have enought context. The existing hive-provided seems to be changed to expect Jackson dependencies to be present in the runtime. Is that expected?

To @xinrong-meng and @viirya , I updated the PR description. You can see that Hive jars are there and only CodeHaus Jacksons are gone.

Thank you, @viirya !

Merged to master for Apache Spark 4.0.0.

Makes sense, thank you @dongjoon-hyun !

Thank you, @xinrong-meng .

@dongjoon-hyun Jackson 1.x can be removed after SPARK-47018 (bump Hive 2.3.10), what should we do for hive-jackson-provided?

It's supposed to be here as a last resort until we release Apache Spark 4.0.0 successfully without reverting Hive 2.3.10, @pan3793 .


ValueError in ReadMe training example

For given training example:
 python main.py --msg-len 32 --epochs 50
executing this command results in following error:
ValueError: Dimensions must be equal, but are 48 and 64
 on line 53 in src/model.py

Same error occurs for other message lengths.

I am experiencing the same issue.

@ayush15k1994 @tjgerot Thanks for reporting the issue. It was an issue with key length and I have pushed a commit  to fix it.


eks.amazonaws.com/token-expiration service account annotation ignored

As per the README, I attempted to set the eks.amazonaws.com/token-expiration annotation on the service account to a value other than "86400". However, no matter what I do, this annotation is completely ignored, and the expirationSeconds of the projected volume in the pod is always 86400. Is there a minimum required EKS version? We are currently using Kubernetes 1.15.

Looks like EKS requires 1.19: https://github.com/aws/containers-roadmap/issues/1274


Pre-generated waveform on MultiCanvas and zoom doesn't fill out each canvas

Hi I'm using multicanvas and pre-generated waveform to deal with long audio file.
Below is the options
this.player = WaveSurfer.create({
      container: $element.selector,
      height: 100,
      cursorColor: 'red',
      backend: 'MediaElement',
      renderer: 'MultiCanvas'
    });

this.player.load(url, waveform);

this.player.on('ready', ()=>{
      this.player.zoom(20);
      this.setVolume(100);
    });

When it comes with multiple canvas, each wave doesn't stretch to its sub canvas.

It only happens with pre-generated waveform. It works fine if I load audio without waveform.
this.player.load(url);

Hey @moyara, is there any chance I could get your pre-generated peak data for testing?

Sure, this is the peak I used
wave.txt

Hi @chrisparton1991,
I ran into the exact same problem - when start to zoom into the waveform.
When it's initially rendered to fillParent, evereything is fine - but as soon as zooming in, it's starts to draw huge gaps between pieces of the waveform. With my peakdata (displaying 4 hours)  these gaps are wider than the browser's viewport-width, see screenshots.
Additionally I'm using splitChannels. I've attached screenshots and pre-rendered peaks in the zip-file.
wavesurfer-issue-814.zip
wavesurfer.init({
container: document.querySelector('#waveform'),
backend: 'MediaElement',
mediaType:'video',
splitChannels: true,
renderer: 'MultiCanvas',
height: 70,
autoCenter: true
});

Little add-on:
Functionality is broken in v1.1.12 but works with version 1.1.4.
I cannot tell anything about behavior of inbetween versions, i have tested it with the two versions above only. Cheers kai

Thanks for the info @kebers!

I've added PR #815.

@chrisparton1991
I've tested it again with your single-line-change  made with PR #815 - looks a lot better - thanks.
Unfortunately I can see a gap - still, at the end of each canvas, when zooming in - to a certain level.
With the peakdata from my post above it can be seen clearly at zoom level 30 (I've used firefox).
wavesurfer.zoom(30);
at a certain position channel 3/4 of that peakdata make use of the maximum amplitude  - which helped to see those gaps more easy.
Can yo confirm or do i have a local issue ?
kind regards kai

I'm looking into this, but it's proving quite tricky. I've fixed the gaps, but the canvases don't always quite match up at high zoom levels.
Additionally, the canvases don't render properly if there are only a couple of peaks per canvas, but that's unlikely to occur in a normal use case.
I'll keep on tinkering.

Duplicate of https://github.com/katspaugh/wavesurfer.js/issues/1181


docs: Update readme

@binaryminds please tell me if my explanation is clear.

Hi @Lenny4,
Thank you for contributing.
Your solution is not good and does not resolve the problem with access to the actual redux state from a listener. Since the listener is a closure it has access only to the component values from the first render. Each concurrent render does not affect already defined listeners.
Here you have a similar situation with setInterval: https://stackoverflow.com/questions/53024496/state-not-updating-when-using-react-state-hook-within-setinterval
If you use Redux you can get the actual value directly from the store instance. Look at my example on Expo Snack: https://snack.expo.dev/@quiknull/react-native-sse-redux-example
Feel free to update docs with this solution.

@wojciechkrol is it better now ?

Hi @wojciechkrol , i'm still waiting for an answer

Hi @Lenny4. Thank you for the update.

Please remove .gitignore, since it is not connected with PR.
Please rename "Warning (react-redux)" to "Usage with React Redux". It shouldn't be a warning. It should help users to understand how listeners work in the context of react-redux.
Make this section be the last sub-section of Usage.

Thank you!

@wojciechkrol done !


Issue when printing on iOS Devices

flutter_bluetooth_printer channel sent a message from native to Flutter on a non-platform thread. Platform channel messages must be sent on the platform thread. Failure to do so may result in data loss or crashes, and must be fixed in the plugin or application code creating that channel.

Can anyone help me to fix this issue?

[ERROR:flutter/shell/common/shell.cc(1065)] The 'maseka.dev/flutter_bluetooth_printer' channel sent a message from native to Flutter on a non-platform thread. Platform channel messages must be sent on the platform thread. Failure to do so may result in data loss or crashes, and must be fixed in the plugin or application code creating that channel.
See https://docs.flutter.dev/platform-integration/platform-channels#channels-and-platform-threading for more information.

This is the issue I get. This is happening for most iOS devices. Sometimes it prints fine & again get the same issue. With Android this is working perfect.

This is the issue I get. This is happening for most iOS devices. Sometimes it prints fine & again get the same issue. With Android this is working perfect.

I have the same issue. I embedded the package directly into my project to fix the thread error, but I still can't get proper output.


Should fix pep8 test errors #57

But let's wait for tests to finish.

Closes #57

@grzanka I think this worked. Pep builds are finally green.


[Compile error] relocation issue: libntl.a

Dear all,
I've got the following error while building cuhe:
coep@coep2-Precision-T1700:~/DHS/cuHE-master/cuhe$ make VERBOSE=1
/usr/bin/cmake -H/home/coep/DHS/cuHE-master/cuhe -B/home/coep/DHS/cuHE-master/cuhe --check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /home/coep/DHS/cuHE-master/cuhe/CMakeFiles /home/coep/DHS/cuHE-master/cuhe/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[1]: Entering directory /home/coep/DHS/cuHE-master/cuhe' make -f CMakeFiles/cuHE.dir/build.make CMakeFiles/cuHE.dir/depend make[2]: Entering directory /home/coep/DHS/cuHE-master/cuhe'
cd /home/coep/DHS/cuHE-master/cuhe && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /home/coep/DHS/cuHE-master/cuhe /home/coep/DHS/cuHE-master/cuhe /home/coep/DHS/cuHE-master/cuhe /home/coep/DHS/cuHE-master/cuhe /home/coep/DHS/cuHE-master/cuhe/CMakeFiles/cuHE.dir/DependInfo.cmake --color=
make[2]: Leaving directory /home/coep/DHS/cuHE-master/cuhe' make -f CMakeFiles/cuHE.dir/build.make CMakeFiles/cuHE.dir/build make[2]: Entering directory /home/coep/DHS/cuHE-master/cuhe'
make[2]: Nothing to be done for CMakeFiles/cuHE.dir/build'. make[2]: Leaving directory /home/coep/DHS/cuHE-master/cuhe'
/usr/bin/cmake -E cmake_progress_report /home/coep/DHS/cuHE-master/cuhe/CMakeFiles  1 2 3 4 5 6 7
[ 33%] Built target cuHE
make -f CMakeFiles/cuHEShared.dir/build.make CMakeFiles/cuHEShared.dir/depend
make[2]: Entering directory /home/coep/DHS/cuHE-master/cuhe' cd /home/coep/DHS/cuHE-master/cuhe && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /home/coep/DHS/cuHE-master/cuhe /home/coep/DHS/cuHE-master/cuhe /home/coep/DHS/cuHE-master/cuhe /home/coep/DHS/cuHE-master/cuhe /home/coep/DHS/cuHE-master/cuhe/CMakeFiles/cuHEShared.dir/DependInfo.cmake --color= make[2]: Leaving directory /home/coep/DHS/cuHE-master/cuhe'
make -f CMakeFiles/cuHEShared.dir/build.make CMakeFiles/cuHEShared.dir/build
make[2]: Entering directory `/home/coep/DHS/cuHE-master/cuhe'
Linking CXX shared library libcuHEShared.so
/usr/bin/cmake -E cmake_link_script CMakeFiles/cuHEShared.dir/link.txt --verbose=1
/usr/bin/c++  -fPIC -fopenmp -m64 -O3 -ffast-math -Wall   -shared -Wl,-soname,libcuHEShared.so -o libcuHEShared.so CMakeFiles/cuHEShared.dir/./cuHEShared_generated_Parameters.cu.o CMakeFiles/cuHEShared.dir/./cuHEShared_generated_DeviceManager.cu.o CMakeFiles/cuHEShared.dir/./cuHEShared_generated_Base.cu.o CMakeFiles/cuHEShared.dir/./cuHEShared_generated_CuHE.cu.o CMakeFiles/cuHEShared.dir/./cuHEShared_generated_Operations.cu.o CMakeFiles/cuHEShared.dir/./cuHEShared_generated_Relinearization.cu.o CMakeFiles/cuHEShared.dir/./cuHEShared_generated_Utils.cu.o /usr/local/cuda-7.5/lib64/libcudart.so /usr/local/lib/libntl.a -Wl,-rpath,/usr/local/cuda-7.5/lib64
/usr/bin/ld: /usr/local/lib/libntl.a(ZZ.o): relocation R_X86_64_32S against .bss' can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libntl.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status make[2]: *** [libcuHEShared.so] Error 1 make[2]: Leaving directory /home/coep/DHS/cuHE-master/cuhe'
make[1]: *** [CMakeFiles/cuHEShared.dir/all] Error 2
make[1]: Leaving directory `/home/coep/DHS/cuHE-master/cuhe'
make: *** [all] Error 2
Can anybody please help me out?
Thanks in advance!!!

SOLVED!!!!
I compiled NTL with shared=on


update: add source plugin symbol to list suggested open parameters

What type of PR is this?
/kind design
/kind documentation
/kind feature
Any specific area of the project related to this PR?
/area libscap
/area libsinsp
What this PR does / why we need it:
This adds support to an optional function symbol for source plugins named list_open_params. Its purpose is to allow source plugins to return a list of suggested parameters that would be accepted as valid arguments to open().
An example use case might be to list the resources openable by the plugin. This can also act as a self-documentation measure to improve the UX of plugin users. Moreover, this can make the plugin more suitable for automatic tooling by obtaining valid open() parameters from the plugin itself without requiring human intervention.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
update: add source plugin symbol to list suggested open parameters

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jasondellaluce
To complete the pull request process, please assign mstemm after the PR has been reviewed.
You can assign the PR to them by writing /assign @mstemm in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@FedeDP: changing LGTM is restricted to collaborators

In response to this:

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

LGTM label has been added.  Git tree hash: aaf89bf1e080dd432a11e434fb831a727a84013c

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Update sbt-scala-native to 0.4.12

About this PR
📦 Updates org.scala-native:sbt-scala-native from 0.3.9 to 0.4.12
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-native", artifactId = "sbt-scala-native" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-native", artifactId = "sbt-scala-native" }
}]

labels: sbt-plugin-update, early-semver-major, semver-spec-minor, commit-count:1

Superseded by #652.


app.use throws SyntaxError

app.use('/(abc)?', fn);

raises
SyntaxError: Invalid regular expression: /^\/(?(?:([^\/]+?)))?\/?(?=\/|$)/: Invalid group

express 4.13.3

Hi! The reason you are getting this error is because the first argument you provided is a syntax error. I can help you construct a proper path, but it almost looks like the code is just gibberish to demonstrate the error. What are you trying to achieve and we can work together on what the syntax would look like to achieve that.
If you wanted to actually provide a real regular expression, then you want to provide the regular expression literal as the first argument: app.use(/^\/(abc)?(?:\/?$|\/)/, fn)

Essentially, I believe that in the path, you cannot start a path segment with an opening parenthesis. /cc @blakeembrey

@dougwilson I used
js app.use(['/abc', '/'], fn)
it solved my problem before I created the issue. But is it not a bug?
I really need to mount the same application to / and /abc. I just read the express docs where is written that I can use path pattern in use()

// will match paths starting with /ad and /abcd
app.use('/a(bc)?d', function (req, res, next) {
next();
})

Hi @golyshevd , the syntax is not full regular expression syntax; it is only a very limited subset. i.m.o. it is not a bug at all, just unsupported in the restructions. I'll let @blakeembrey weign in as well, as he maintains the module that does the string to regular express compilation.
If your goal is to mount to both places, you should definitely be using the array syntax and not a single string syntax, as that is the purpose of the array syntax, especially since we can optimize the paths better.

ok then, thank you for explanation!

This is supported for 1.x of path-to-regexp, but not the current version inside Express (README here: https://github.com/pillarjs/path-to-regexp/tree/0.1.x). The 0.1.x branch of path-to-regexp does not support unnamed regular expression groups like that. If you gave it a name, like '/:name(abc)?', it should be ok. However, I do believe this is likely a bug since some subset of RegExps like this do work on the 0.1.x series - I'm just not sure whether it should be fixed since they aren't documented at all.

Ah, gotcha, @blakeembrey . So from the sounds of it, it can go either way, as either a bug (oops, we didn't support empty labels) or as a feature not added until 1.x (hey, we added support for empty labels!). @golyshevd with the Express 5 series coming up, we will be using the 1.x of path-to-regexp, which sounds like it would resolve this issue.
I'm going to close this for now, but let me know if you want it re-opened :)


How to get version information?

It would be nice if the module had a __version__ member. I find that the easiest to use and many still support it.
I know that there is importlib.metadata but I find it to have many hurdles:

It requires Python 3.8. There is a backport but it requires trying two different imports and adds a new dependency for older Python versions. the dataclasses backport is easier to use because the name is interchangible.
It's hard to use. It requires the package name as distributed. But here the package name is python-xz as opposed to the module name which is just xz. I could not find a reliable way to get that name from the module. I tried xz.__name__ and xz.__package__, which both return xz. Maybe there is some other way?

From my understanding, having __version__ was a proposition in PEP 396 that is rejected, and you cannot rely on modules to provide __version__. Now the importlib.metadata module seems the way to go.

This PEP was formally rejected on 2021-04-14. The packaging ecosystem has changed significantly in the intervening years since this PEP was first written, and APIs such as importlib.metadata.versions() provide for a much better experience
--- https://www.python.org/dev/peps/pep-0396/#pep-rejection

>>> from importlib.metadata import version
>>> version('python-xz')
'0.1.1'

For older versions of Python, instead of the backport you can use pkg_resources if setuptools is installed:
>>> from pkg_resources import get_distribution
>>> get_distribution('python-xz').version
'0.1.1'

Use of pkg_resources is discouraged in favor of importlib.resources, importlib.metadata, and their backports (resources, metadata). Please consider using those libraries instead of pkg_resources.
--- https://setuptools.readthedocs.io/en/latest/pkg_resources.html

It requires the package name as distributed.

That's a good point. Although one could argue that if you import a module, it means that it has been installed before, so you know the package name.

With all that being said, there may still be some value in getting the version from an imported module (and not from its distribution name), i.e. from xz after an import xz. Getting xz.__version__ would solve this need.
I agree that although the PEP 396 is rejected, __version__ is provided by many libraries.
So I will look into adding it :eyes:

Another point is that importlib.metadata only gets the version from the packaging system. If you do some funny module loading stuff you might get a different version than the module you have at runtime.
I also saw PEP 8 being mentioned in reference to __version__ but there it is "only" mentioned as an example for module level dunder names.
I guess, I just like the ease of the old method and I would personally have preferred PEP 396 to pass. It feels like the shift to importlib.metadata puts the work to the user instead of the developer, which feels wrong assuming that there are many times more users than developers. But that would be a discussion for the Python mailing list if I had sufficient pushiness about this issue.
In the end, I only need it for debugging, so it wouldn't be all that problematic if it was missing. I already have a "hasattr" check in place if it is missing anyway.
Just, the problem with module name vs distribution name struck me as very problematic in comparison to using __version__.
Currently, my plan is to make python-xz the default requirement for ratarmount because I can't do it with lzmaffi because it depends on cffi, which will most likely be missing, meaning the pip installation will fail.

Version 0.1.2 now exports the version as the module attribute __version__ :rocket:


How to start it?

Where's the docs for I run it?
How to start the project?

I try it, but I catch follow error:

Hi Lucas, I'v made the change can you try again ?


Some style issues in the multiple different types of buttons

The style of buttons has different values.
for example for BitActionButton height is set but for BitLoadingButton minHeight is set.
and also the height of these two is different.
It is better to set a line height for the text and a default padding or min-height for all buttons and read the values from the theme.
And also it could be valid for other common properties in buttons.

this issue is resolved


Stiebel Eltron ISG Cooling Room Temperature Target not synced with  ISG

Hello,
I've an ISG Web. I've manually specified on the ISG the Target Room temperature to 22°. On HAS, the Stiebel Eltron ISG Cooling Room Temperature Target stay at 25°.
I try to change on the HAS the value for Stiebel Eltron ISG Cooling Room Temperature Target to 21.9°, but not changes was made on the ISG Gateway.

Hello together :)
I have the same problem with the water temperature?

@fabricekrebs Your Servicewelt Screenshot shows Cooling Circuit 2. In the Modbus Manual, there is no indication of a Circuit number. I'm using the registers 1514 and 1516.
@Chris909090 @fabricekrebs Could you please install the latest release 2023.10 and download the diagnosis information. I have added a "system_parameters" entry which shows all the 15xx registers which are read. Is there any value correctly showing the temperature?

@pail23
Thanks four your help!
As you could see in the diagnostic there is the value for the water temperature set to 41,2°C.
But in the servicewelt there are still 41°C.
Maybe here is a problem with the vslue? It iftenshows "32768". Are you able to reproduce the error?
Thanks for your time!

Sry here the images

@pail23
Were you able to do anything with what I told you?

@Chris909090 The modbus registers are matching the values in homeassistant.  I have no clue why servicewelt is showing a different value. What happens if you set the water temperature in Homeassistent to e.g. 50? Does the heat pump react?

OK I do not understand why but now it works I guess it was not your app but Stiebel Eltron itself
Thank you! :)


Error: Can't call View#autorun from inside render()

I get the following exception in version v0.6.0
meteor.js?hash=e3f53db…:930 Exception in template helper: Error: Can't call View#autorun from inside render(); try calling it from the created or rendered callback
    at Blaze.View.autorun (http://localhost:3000/packages/blaze.js:1907:11)
    at autorun (http://localhost:3000/packages/peerlibrary_computed-field.js:52:28)
    at startAutorun (http://localhost:3000/packages/peerlibrary_computed-field.js:59:16)
    at new ComputedField (http://localhost:3000/packages/peerlibrary_computed-field.js:89:5)

before I updated, I was using v0.3.1 and it was working

Inside what are you using your computed field? So what is the context outside?

Yeah sorry, I'm working since 13 hours for now. I need to sleep.
I have have a little function that formats a date with the users date format. I'm using this function on server side and as a blaze helper. The function looks like the following:
export default (date, options) => {
  const dateFormat = Meteor.isServer
    ? () => getDateFormat(options.userId, options.teamId)
    : new ComputedField(() => getDateFormat())
  return moment(date).format(_.isString(options) ? options : dateFormat())
}

I'm calling this blaze helper directly inside the template and as a normal function inside some react components. The error only occurs if I use the function as a blaze helper.

Hm, yes, inside template helpers computed field currently does not work well because of the last change.
As a workaround for now, you can do something like:
return Blaze._withCurrentView(null, () => {
  // your original code
});

This will trick computed field into not trying to use template level autorun.
Personally, I prefer attaching computed fields to template instances inside onCreated or onRendered and then simply access them inside template helpers. But I see that you cannot make this easily here because of the options.


does this support "template-url" feature like angularjs?

does this support "template-url" feature like angularjs?

can you make an example?

on the server side:
response a template like:
{this.state.hello}
on the client side:
import ...
import translate from 'react-templates';
class hello extends Component
{
constructor(props)
{
super(props);
this.state={
renderCode:null
}
}
componentDidMount
{
$.get("api/helloTemplate",function(template){
this.setState({renderCode:translate(template)};
}
}
render()
{
return {this.state.renderCode};
}
}

hi@nippur72 , I am very sorry because  I think that my idea is wrong,thanks all the same for your help.


Don't render reminder button when secondary CTA present

Only render the reminder button if there's no secondary CTA. This reflects the current behaviour on frontend:
https://github.com/guardian/frontend/blob/23500ccc75b297db9e11e9027f65ac3d6dc9765b/static/src/javascripts/projects/common/modules/commercial/templates/acquisitions-epic-buttons.js#L72

I also noticed on frontend that for configured tests with the default template at least, there's a switch to control whether or not to show a reminder. So we should possibly follow up with something similar at some point.


Account creation wizard

https://github.com/hypha-dao/dho-web-client/issues/593
https://github.com/hypha-dao/dho-web-client/issues/592
https://github.com/hypha-dao/dho-web-client/issues/595
https://github.com/hypha-dao/dho-web-client/issues/594
@pugakn I intentionally  did not created components as I had issues with text-input-component because it did not encompass current use cases, so I will split into components once I complete DHO wizard and figure out multiple use cases.
@leonieherma1 Currently missing

[ ] copy for each step
[ ] where to link to create wallets (bitcoin, eos, eth)(step 3)
[ ] logic to redirect user to complete profile

@arsenijesavic thank you!
Logic for now should be:
When I register for the DHO and AFTER I get enrolled and I login  for the first time the account creation process should start.


Issue with SPFx Web Part as a Teams Personal App in GCC

Category

[x] Bug

Describe the bug
I deployed a SPFx web part to Teams in GCC as a personal app.  When I click on the app in teams, the page displays a "_layouts’s server IP address could not be found".  Deployed the same SPFx web part to a commercial tenant and works as expected in teams.  I used the Teams web client in both cases.
Steps to reproduce

Create a brand new spfx web part project with yeoman.  Enable tenant wide deployment and choose react as the framework.
In the web parts manifest file, update the supported hosts to include 'TeamsPersonalApp'
In the web parts .ts file, at line 24, replace this.properties.description with "Test".  I read somewhere that the properties will be undefined in Personal Teams Apps so wanted to rule out that.
Build and Package the web part with --ship flag
in a GCC tenant, upload the .sppkg file to the app catalog.
Make sure 'Make this solution available to all sites in the organization' is checked when you deploy it.
Sync to Teams
View App in Teams
Should see the error: "_layouts’s server IP address could not be found"

Expected behavior
Web part should render the web part.
Environment details (development & target environment)

Windows 10
GCC SharePoint Online
SPFx 1.11, React
Edge
VS Code
Teams Web Client

Additional context
Repro steps work in a commercial tenant.

In GCC, this is the URL found in the network calls.  It's missing the tenant name.
_https://_layouts/15/TeamsLogon.aspx?SPFX=true&dest=/layouts/15/teamshostedapp.aspx%3Fteams%26personal%26componentId=6ed6cdb3-8353-48d4-a9f0-90b1d7b87c5a%26forceLocale=en-us
Here is what it looks like in the commercial tenant.
_https://{{tenant name}}.sharepoint.com/_layouts/15/TeamsLogon.aspx?SPFX=true&dest=/layouts/15/teamshostedapp.aspx%3Fteams%26personal%26componentId=6ed6cdb3-8353-48d4-a9f0-90b1d7b87c5a%26forceLocale=en-us

In GCC, this is the URL found in the network calls.  It's missing the tenant name.
_https://_layouts/15/TeamsLogon.aspx?SPFX=true&dest=/layouts/15/teamshostedapp.aspx%3Fteams%26personal%26componentId=6ed6cdb3-8353-48d4-a9f0-90b1d7b87c5a%26forceLocale=en-us
Here is what it looks like in the commercial tenant.
_https://{{tenant name}}.sharepoint.com/_layouts/15/TeamsLogon.aspx?SPFX=true&dest=/layouts/15/teamshostedapp.aspx%3Fteams%26personal%26componentId=6ed6cdb3-8353-48d4-a9f0-90b1d7b87c5a%26forceLocale=en-us

I decided to manually make the teams app manifest file instead of synchronizing to Teams from the app catalog.
It appears that GCC is not honoring the {teamSiteDomain} token in the contentUrl property under static tabs in the manifest but if you replace {teamSiteDomain} with your tenant domain (xxx.sharepoint.com) it works.

@goodjohnscott, coming back to this issue as it got lost due labeling issues (sorry about that). Can you check if the issue still occurs? Our understanding is that "sync to Teams" should now work in GCC environments.


Does not compile on Solaris

Reminder issue: This needs to be fixed, probably by not calling the syscall directly, but via golang.org/x/unix:
GOOS=solaris go build
# github.com/restic/restic/internal/ui/termstatus
../../internal/ui/termstatus/terminal_unix.go:35:35: undefined: syscall.SYS_IOCTL

Also, we need to build for Solaris on Travis to catch this earlier next time.

I think this is an easy fix - unix.IoctlGetWinsize seems to do the job.
It builds and runs on SmartOS now.

Cool, thanks!

This issue is resolved in master, closing.


HAWKULAR-676 - Topology view

It's enabled only under experimental mode. To enable experimental mode, click on the hawkular brand (top left).

Should this be a standalone plugin? Its just a tab right? Its much easier to do integrations for the future if its codebase is part of Hawkular. And we have explicit control over the css(less) styles loading overriding one another.
Also, shouldn't the directives be part of Hawkular-charts?


Feature/merging develop

This PR is for merging #401 #404 into release/0.7.3.

Thanks for the fast review!!


cdc: fix cdc integration test  test_rawkv_sacn

Signed-off-by: zeminzhou<EMAIL_ADDRESS>
What is changed and how it works?

Issue Number: Close #14146
What's Changed:

make cdc integration test `test_rawkv_sacn` stable

Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)

Side effects
NO
Release note
make cdc integration test `test_rawkv_sacn` stable

@pingyu This problem may be caused by the current thread executing too slowly. If after executing suite.set_tso(10);, the current thread is not advanced, but causal_ts_provider keeps advancing the tso of pd, causing the current tso of pd to exceed 1000. What do you think?

@pingyu This problem may be caused by the current thread executing too slowly. If after executing suite.set_tso(10);, the current thread is not advanced, but causal_ts_provider keeps advancing the tso of pd, causing the current tso of pd to exceed 1000. What do you think?

LGTM~

/run-all-tests

/merge


Switch App Distribution SDK from AppAuth to FirebaseInstallations

Add GHA for App Distribution SDK
Update SDK minimum version to iOS 9.0
Update changelog for beta release
Change imports to Sources/
Switch from AppAuth -> FirebaseInstallations

#no-changelog: We will update the changelog once this is merged and ready to be included in a release.

This is a fairly large PR, so we're prepared a guide to help make it easier to review: https://docs.google.com/document/d/1rS4z4igbpPM8AX3NZ88bOQ2bQ5jqQGsM1gvbZpqkvsw/edit

@maksymmalyhin Would you take a look specifically at the FIS usage?


Fix getCommitInfo to get the hunk even with EOL changed case.

Hi,
This tool is very nice. However, I encountered a situation where it did not work well in my case.
Example :

Changing EOL only
New file with only one line of code

In this modification, I fixed it to work well in the above cases.
It may not be a good fix as it is quite hard coded.

Thanks for this @mugioka  - I'm concerned this change will result in single line changes being ignored so I need to do some more testing and reproduce your issue

Hi,
It seems that this PR is not needed. I close this PR.
Thanks.


Started Posting code in chat instead of IDE

Describe the bug

Started putting the code into chat, once I assume the context window got too large
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-joox1e
Steps to reproduce

Start a project,
get to second prompt and give a complex prompt with 2-3 actionables
Get code overflow in chat

Expected behavior
To continue creating and adding flies and code in IDE
Screen Recording / Screenshot

Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 129
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 101835625,
  "usedJSHeapSize": 77480189,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = sohil404
Chat ID = d235d1af331e

Additional context
No response

Prompted to continue in chat and it did

Hi! 👋 Thanks a lot for the report!
We're tracking this issue internally and will let you know when we have a fix in place.

We have deployed a fix for this issue! It should work as expected now. :tada:
If you run into more issues, feel free to open a new one! :raised_hands:


pretrained models.

Hi, I noticed that training 2D pose estimation requires a pretrained model (pretrained='pretrained/tcformer-4e1adbf1_20220421.pth'). I would like to ask how to obtain this model?
Looking forward to your reply !

These are imagenet_pretrained models. Please check the links here.


Provide "Color" picker as schema type

For apps which allow colors to be customized, it would be helpful if there was a color picker option available within schema. Right now, it appears that the best option is to utilize a list of predefined values with a dropdown schema.
  colors = [
    {"text": "White", "value": "#fff"},
    {"text": "Red", "value": "#f00"},
    {"text": "Green", "value": "#0f0"},
    {"text": "Blue", "value": "#00f"},
    {"text": "Yellow", "value": "#ff0"},
    {"text": "Cyan", "value": "#0ff"},
    {"text": "Magenta", "value": "#f0f"},
  ]
…
    {
      "type": "dropdown",
      "id": "color",
      "icon": "palette",
      "name": "Color",
      "description": "The color to display.",
      "options": colors,
      "default": DEFAULT_COLOR,
    },

My ideal state would be to have the Tidbyt controlled via HomeKit, and use HomeKit to set the color of the display. As long as the app accepts a single color variable, I believe this should be possible.

There was one added a few weeks ago: https://tidbyt.dev/docs/reference/schema#color

Time to close as completed ?


Allow Quick Accent to switch on/off character groups separately

Description of the new feature / enhancement
Currently, we can only set this using a dropdown list:

I hope these choices can be set individually using checkboxes:

Scenario when this would be used?
I need more than one group of characters, but not all of them.
Supporting information
If another feature - binding user-defined characters to keys - can be developed, it would be much more useful!

I also need to be able to select multiple character set.  I write both in French and Swedish, but I don't want all the other character.

/dup #21261


Error: 'slice' called on an object that does not implement interface Blob.

I am previewing the image on page,
and after clicking on save button I am uploading image + sending http data of other form fields.
The image gets uploaded successfully but when sending http request to save all data, the error occurs.
"Error: 'slice' called on an object that does not implement interface Blob."
Tried a lot to solve this not got success.
Please help me on this.
Upload code:
            Upload.upload({
                url: 'myproject/controller/image_upload',
                file: file,
                method: 'POST',
                sendFieldsAs: 'form'
            }).progress(function (evt) {
                var progressPercentage = parseInt(100.0 * evt.loaded / evt.total);
                console.log('progress: ' + progressPercentage + '% ' + evt.config.file.name);
            }).success(function (data, status, headers, config) {
                console.log('file ' + config.file.name + 'uploaded. Response: ' + data);
            }).error(function (data, status, headers, config) {
                console.log('error status: ' + status);
            })

Code to save form data
            $http({
                method: 'POST',
                url: "myproject/controller/get_data",
                data: $.param($scope.store),
                headers: {'Content-Type': 'application/x-www-form-urlencoded'}
            })

So is the error occurs on the Upload.upload function or $http() ? Can you create a jsfiddle?

It should be fixed in the latest versions.

Did you get a solution for tis problem? I am facing the same problem while sending Input type="file" value using Ajax. Your help is appriciated.

Because the used file and the obtained file are not the same type, convert it at the point of use, webupload encapsulates the file twice.
use as file.source.source

How does one convert it?

Found that you should just add "contentType: false, processData: false," to your ajax request.
Look at this https://stackoverflow.com/questions/19722920/submitting-a-file-with-jquery-ajax-gives-typeerror


Generate dart file containing references to all assets and fonts available to app

Inspired on R.drawable.image_logo on native android platform.
Based on top of work done on #4890, it's independent of #18897 but highly related.

Copying my own comment from https://github.com/flutter/flutter-intellij/issues/2378#issuecomment-400178867:

There are some challenges though:
a) since android restricts the allowed filenames it's much easier to generate field names accessible in java. Flutter accepts any filename which makes it quite tricky to handle for example filenames composed of characters such as emojis, @ or [.
b) android gracefully handles collisions by overwriting assets when a conflict is found. In flutter we'll have collisions for files coming from different folders, different extensions, and more so for the forbidden characters as mentioned in the point above.

a is tricky but can be tackled, but b needs a lot of thinking on how the developer will access different files with different filenames that would naively map to the same class+field on generated code.

I'm still interested in getting this done and I have something basic that will do for most projects. But I need feedback on how to gracefully degrade for all types of conflicts.
Ideas anyone?

What do you mean by gracefully degrade ? Generally on Android when you have a conflict it just doesn't compile anymore and give you an error message, why not do the same ?
I would like to see this append :) can we see your basic solution somewhere ?

I suggest adding folder support like: R.drawable.images.nature and if multiple files with same path, then R.drawable.images.nature.jpg or like a suffix R.drawable.images.nature_jpg.
With "images" being folder name

Or just add better support for build_runner so that people can write plugins to generate asset names, language strings, parsers, etc. and they will be built during flutter run.

@szotp  I stopped following the state of things for build_runner, but what you suggest is aligned with what I'd like to have
@jaumard
consider the following examples:
/assets/images/3.jpg
/assets/images/this.png
/assets/images/this.jpg
/assets/images/this.JPG
/assets/other/this.png
And assuming pubspec has an entry for assets/images and another for assets/other, how would you disambiguate things?

FYI I'm integrating build_runner support into the flutter tool, so if you're interested I suggest you follow/thumbs up https://github.com/flutter/flutter/issues/27141

@fmatosqg for me those shouldn't compile and throw an "ambiguous" error for the user to rename those
consider the following examples:
/assets/images/3.jpg
/assets/images/this.png
/assets/images/this.jpg
/assets/images/this.JPG

but if they are under another folder like /assets/other/this.png for me should be ok to have something like Assets.other.this and Assets.images.this this is a wrong example as it's a reserved keywords but you get it ^^

@jonahwilliams that's very good news for a whole host of reasons :)  I've wanted that since hearing how build_runner works.

Anyone started working on this already? Flutter really needs something like https://github.com/mac-cain13/R.swift.

Update: I found a package named r_flutter which actually does what this issue asked for, but it didn't use new build config.
I have currently working version on my fork: https://github.com/szotp/r_flutter
It generates asset names, font names and localization keys (thanks to @timfreiheit original work), and uses Builder which automatically updates the file when changes are made.

@YK-Unit Thank you and your team for the amazing work.
I will try it.
Thanks so much!


UI goes crazy when clearing out the field and start typing

Hi!
Thanks for this component. See from your demo page, the controlled example goes bad when you clear out the field and type any number

Thanks for catching this and reporting it! Fixed in 1.2.6


Add Django 1.7 compatibility

Mention SOUTH_MIGRATION_MODULES settings in installation documentation
Add SOUTH_MIGRATION_MODULES settings in test_settings.py
Move old migrations directory to south_migrations dedicated directory
Update tox.ini to use Django 1.7 release
Add new migrations directory which contains the new schema
Don't hesitate if I need to rebase from your master after merging others PRs.

Changes Unknown when pulling b096f4d81e90ac7fe4ef693f44303aa39fcfeae8 on thoas:dj17 into ** on jsocol:master**.


puzzling apparent conflict between slog, env_logger

I came across some puzzling behavior, where changing the order of a few lines when constructing the Logger in fn main can either work fine or cause major bugs.
this is a code snippet to illustrate the problem as simply as I can. there are three fn mains in example, the top one is causing problems and the bottom two (slight changes to order of operations) work fine.
#[macro_use]
extern crate slog;

use slog::Drain;

fn stdout_logger() -> slog::Logger {
    let decorator = slog_term::TermDecorator::new()
        .stdout()
        .build();
    let drain = slog_term::CompactFormat::new(decorator)
        .build()
        .fuse();
    let drain = slog_async::Async::new(drain)
        .chan_size(1024 * 64)
        .thread_name("my-logger".into())
        .build()
        .fuse();
    slog::Logger::root(drain, o!("version" => env!("CARGO_PKG_VERSION")))
}

// this one causes baffling behavior, including failures that are beyond just
// logging-related problems, ie function that is working in the other examples
// returns an error in this version instead.
fn main() {
    let logger = stdout_logger();
    let env_logger = env_logger::Logger::from_env(env_logger::Env::new().default_filter_or("debug"));
    rustwide::logging::init_with(env_logger);
    // ..
}

// this one works fine (emit a `debug!` log prior to the env_logger stuff)
fn main() {
    let logger = stdout_logger();
    debug!(logger, "initializing ...");
    let env_logger = env_logger::Logger::from_env(env_logger::Env::new().default_filter_or("debug"));
    rustwide::logging::init_with(env_logger);
    // ..
}

// this one also works fine (`logger` constructed following the env_logger stuff)
fn main() {
    let env_logger = env_logger::Logger::from_env(env_logger::Env::new().default_filter_or("debug"));
    rustwide::logging::init_with(env_logger);
    let logger = stdout_logger();
    // ..
}

Unfortunately, tracking and explaining what happens is somewhat complicated - this is a big program with tons going on in many threads. Also the behavior of the buggy version is very confusing. Not only do the logs not show up (which makes diagnosing what happened super difficult!), but the program also fails in terms of its non-logging-related output. i.e. a function that returns Ok(_) in the working versions returns Err(_) in the buggy one.
The part of the program that fails is on another thread from where the logger was originally constructed, also it is using a tokio runtime (which was constructed on the other thread), so there are possible async/tokio issues in play.
It likely occurs in a section of code where rustwide is actively capturing logs, but I don't know for sure (since I don't get any logs).
I get the same behavior with debug and release builds.
The rustwide::logging::init_with function is here. I haven't looked closely at what is going on there, but the code in that file is used to capture logs during sandboxed rust builds.
The reason I have both slog logger and the env_logger is because my code uses slog but some of the libraries are generating logs other ways that I would like to be able to view/capture.
do you guys have any kind of hypothetical theory for what might be behind this behavior? I am mostly interested in ensuring it doesn't happen (i.e. avoiding the buggy version). Seems this could possibly be the combination of overlapping global or thread local static values used to store state and macros that could paper-over type compatibility problems, but that's only a stab in the dark.

Hard to say. My instincts tell me: some circular initialization / locking, triggered in one of the lazy-initialization code.

I will look into this when I have time. Definitely concerning 😦

Closing this issue as the problem turned out to be wholly unrelated to slog. Apologies for a false alarm.


os/mac/pkgconfig/14: update libcurl for 14.5 SDK

macOS 14.5 SDK has been an Xcode-exclusive SDK until now, so we never updated this pc file. CLT 16 will however include macOS 14.5 SDK so we can update this now.
While the 8.6.0 runtime supports NTLM_WB, the 8.6.0 curl-config dropped the reference to it ahead of Apple dropping it in macOS 14.6's curl 8.7.1 update, which never received a corresponding SDK. Not reporting a feature seems like the safest option.
This PR may have to wait until after the CLT is released fully.

This PR may have to wait until after the CLT is released fully.

CI agrees

Seeing
Failures:

  1) pkg-config returns the correct version for libcurl
     Failure/Error: expect(pc_version("libcurl")).to eq(version)

       expected: "8.6.0"
            got: "8.4.0"

       (compared using ==)
     # ./test/os/mac/pkgconfig_spec.rb:53:in `block (2 levels) in <top (required)>'

in CI now.
https://github.com/Homebrew/brew/actions/runs/10958495800/job/30428868352?pr=18364#step:12:118


Revise all Javadocs in order to fix errors

There are many warning about how a reference is missing; Well, I saw an instance of COMPOST_CHANCE being used when 1.19.3 migrated to COMPOST_CHANCES; This should be a relatively simple task

Part of the issue in mind (links not pointing to intended places) has been fixed, while other part (links pointing to non-imported modules being considered as errors) might be considered as a completely different issue, that is, if we consider it one; I'll close this issue for now


feat(#847): log_dataset

Current dependencies on/for this PR:

#848  👈
main

This stack of pull requests is managed by Graphite.

Merge activity

Feb 29, 9:04 AM EST: @HLasse merged this pull request with Graphite.


PROGRAMMES-5802 update clifton with aggregateGalleriesCount

update clifton with aggregateGalleriesCount
Updated pages services

Can one of the admins verify this patch?


[Build] Not building "CustomValidationPopup does not exist"

Building the MahApps.Metro project (commit cb92648) results in error
"CustomValidationPopup" does not exist in namespace "http://metro.mahapps.com/winfx/xaml/controls
The  error was reproduced on multiple machines with
Windows 10 Build 16299
Visual Studio 2017 Professional (15.7.4)
.Net Framework SDKs for 4.6.1, 4.6.2, 4.7, 4.7.1
We tried on three different machines with the same software setup as above. The error remains the same.

@auxua Appveyor and local build works, so what are you exactly doing? Building MahApps inside your app? Or standalone?

Standalone, clean clone from this repo using the Visual Studio build pipeline

@auxua Does this also happen if you run powershell .\build.ps1 inside the src folder?

When using the ps1 script I get an error durcing the Restore chapter  naming, that the target restore is not existing in the project (MSB4057)

@auxua Any chance to try again with the latest dev source?


x/net: module golang.org/x/net@latest found (v0.5.0), but does not contain package golang.org/x/net

What version of Go are you using (go version)?
go version go1.19.5 darwin/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/mike/Library/Caches/go-build"
GOENV="/Users/mike/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/mike/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/mike/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.19.5/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.19.5/libexec/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.19.5"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/80/hvrr1sbs3h5118dc82nrfb_m0000gn/T/go-build3374878071=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
When I run install,c ommand to install a library/module by go install golang.org/x/net@latest
it produces error
go: golang.org/x/net@latest: module golang.org/x/net@latest found (v0.5.0), but does not contain package golang.org/x/net
What did you expect to see?
i expect to install this package
What did you see instead?
this message:
go: golang.org/x/net@latest: module golang.org/x/net@latest found (v0.5.0), but does not contain package golang.org/x/net

working as intended, there's nothing for you to install at x/net


the ssd error when I change the 'with_mask=True'

The error is like these:
File "/home/algorithm/mmdetection/mmdet/datasets/custom.py", line 169, in getitem
data = self.prepare_train_img(idx)
File "/home/algorithm/mmdetection/mmdet/datasets/custom.py", line 240, in prepare_train_img
scale_factor, flip)
File "/home/algorithm/mmdetection/mmdet/datasets/transforms.py", line 104, in call
for mask in masks
File "/home/algorithm/mmdetection/mmdet/datasets/transforms.py", line 104, in
for mask in masks
mmcv/image/transforms/resize.py",  line 101, in imrescale
type(scale)))
TypeError: Scale must be a number or tuple of int, but got <class 'numpy.ndarray'>

Also, when I get rid of the
resize_keep_ratio=False，it will dispear
File "/home/algorithm/mmdetection/mmdet/models/detectors/single_stage.py", line 55, in forward_train
*loss_inputs, gt_bboxes_ignore=gt_bboxes_ignore)
File "/home/algorithm/mmdetection/mmdet/models/anchor_heads/ssd_head.py", line 159, in loss
unmap_outputs=False)
File "/home/algorithm/mmdetection/mmdet/core/anchor/anchor_target.py", line 71, in anchor_target
labels_list = images_to_levels(all_labels, num_level_anchors)
File "/home/algorithm/mmdetection/mmdet/core/anchor/anchor_target.py", line 84, in images_to_levels
target = torch.stack(target, 0)
RuntimeError: invalid argument 0: Sizes of tensors must match except in dimension 0. Got 7836 and 6758 in dimension 1
I think that is because if we keep the the resize ratio, it will get the unfixed size.


creating a workflow file creates a warning log message and child device in tedge-mapper-c8y

Describe the bug

Creating a workflow file under the /etc/tedge/operations folder, results in an erroneous errors message in the tedge-mapper-c8y as the mapper things this should be a customer operation and not a custom workflow definition.
The workflow definition describes the process where the workflow definitions are to be kept.
Below shows the warning log message in question:
Jan 20 19:58:33 rpi4-d83add90fe56 tedge-mapper[1306]: 2024-01-20T19:58:33.717707703Z  WARN c8y_api::smartrest::operations: Ignoring custom operation definition as the filename uses an invalid character. Only [A-Za-z0-9_] characters are accepted. file=/etc/tedge/operations/firmware_update.toml

To Reproduce

Create a dummy workflow file
touch /etc/tedge/operations/my_workflow.toml

Check the tedge-mapper-c8y logs
journalctl -u tedge-mapper-c8y -n 100

Expected behavior

Creating a valid workflow (as per the documentation), should not invoke the custom operation handler logic, and should not log a warning message.
Screenshots

Environment (please complete the following information):

Property
Value

OS [incl. version]
Debian GNU/Linux 12 (bookworm)

Hardware [incl. revision]
Raspberry Pi 4 Model B Rev 1.5

System-Architecture
Linux rpi4-d83add90fe56 6.1.0-rpi7-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24) aarch64 GNU/Linux

thin-edge.io version
tedge 1.0.0-rc.2~116+g02d20ea

Additional context

There seems to be an additional side-effect from reacting to the firmware_update.toml file, where a child device called operations is being created in Cumulocity IoT. The following log entry shows the offending 114 message being sent to the c8y/s/us/operations topic resulting in the child device creation:
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.518798921Z DEBUG C8yMapper => Mqtt: send Message { topic: Topic { name: "c8y/s/us/operations" }, payload: "114,""", qos: AtLeastOnce, retain: false }

Below is the extended log with more context on the lead up to the above message being sent:
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.491025505Z DEBUG c8y_mapper_ext::converter: Mapping message on topic: te/device/main///cmd/restart
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.491125547Z DEBUG tedge_utils::file: Creating the directory "/etc/tedge/operations/c8y"
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.491161234Z DEBUG tedge_utils::file: Applying desired user and group for already existing dir: "/etc/tedge/operations/c8y"
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.498959668Z DEBUG C8yMapper => Mqtt: send Message { topic: Topic { name: "c8y/s/us" }, payload: "114,c8y_Command,c8y_DownloadConfigFile,c8y_Firmware,c8y_RemoteAccessConnect,c8y_Restart,c8y_UploadConfigFile", qos: AtLeastOnce, retain: false }
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.49909562Z DEBUG CumulocityMapper: recv Some(MqttMessage(Message { topic: Topic { name: "te/device/main///cmd/software_list" }, payload: "{}", qos: AtLeastOnce, retain: false }))
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.499129696Z DEBUG c8y_mapper_ext::converter: Mapping message on topic: te/device/main///cmd/software_list
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.49912777Z DEBUG MQTT: recv Ok(Some(Message { topic: Topic { name: "c8y/s/us" }, payload: "114,c8y_Command,c8y_DownloadConfigFile,c8y_Firmware,c8y_RemoteAccessConnect,c8y_Restart,c8y_UploadConfigFile", qos: AtLeastOnce, retain: false }))
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.499185347Z DEBUG CumulocityMapper: recv Some(MqttMessage(Message { topic: Topic { name: "te/device/main///cmd/log_upload" }, payload: "{"types":["c8y_Command","firmware_update","software-management"]}", qos: AtLeastOnce, retain: false }))
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.499206737Z DEBUG c8y_mapper_ext::converter: Mapping message on topic: te/device/main///cmd/log_upload
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.499231738Z DEBUG rumqttc::state: Publish. Topic = c8y/s/us, Pkid = 21, Payload Size = 108
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.499265536Z DEBUG tedge_utils::file: Creating the directory "/etc/tedge/operations/c8y"
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.499297204Z DEBUG tedge_utils::file: Applying desired user and group for already existing dir: "/etc/tedge/operations/c8y"
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.507661705Z DEBUG C8yMapper => Mqtt: send Message { topic: Topic { name: "c8y/s/us" }, payload: "118,c8y_Command,firmware_update,software-management", qos: AtLeastOnce, retain: false }
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.507796526Z DEBUG CumulocityMapper: recv Some(MqttMessage(Message { topic: Topic { name: "te/device/main///cmd/software_update" }, payload: "{}", qos: AtLeastOnce, retain: false }))
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.507826972Z DEBUG c8y_mapper_ext::converter: Mapping message on topic: te/device/main///cmd/software_update
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.507829713Z DEBUG MQTT: recv Ok(Some(Message { topic: Topic { name: "c8y/s/us" }, payload: "118,c8y_Command,firmware_update,software-management", qos: AtLeastOnce, retain: false }))
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.507927144Z DEBUG tedge_utils::file: Creating the directory "/etc/tedge/operations/c8y"
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.507932126Z DEBUG rumqttc::state: Publish. Topic = c8y/s/us, Pkid = 22, Payload Size = 51
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.507960887Z DEBUG tedge_utils::file: Applying desired user and group for already existing dir: "/etc/tedge/operations/c8y"
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.518209076Z DEBUG C8yMapper => Mqtt: send Message { topic: Topic { name: "c8y/s/us" }, payload: "114,c8y_Command,c8y_DownloadConfigFile,c8y_Firmware,c8y_LogfileRequest,c8y_RemoteAccessConnect,c8y_Restart,c8y_SoftwareUpdate,c8y_UploadConfigFile", qos: AtLeastOnce, retain: false }
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.518354139Z DEBUG C8yMapper => Mqtt: send Message { topic: Topic { name: "te/device/main///cmd/software_list/c8y-mapper-2024-01-20T21:09:38.518122275Z" }, payload: "{"status":"init"}", qos: AtLeastOnce, retain: true }
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.518396826Z DEBUG MQTT: recv Ok(Some(Message { topic: Topic { name: "c8y/s/us" }, payload: "114,c8y_Command,c8y_DownloadConfigFile,c8y_Firmware,c8y_LogfileRequest,c8y_RemoteAccessConnect,c8y_Restart,c8y_SoftwareUpdate,c8y_UploadConfigFile", qos: AtLeastOnce, retain: false }))
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.518401919Z DEBUG CumulocityMapper: recv Some(FsWatchEvent(Modified("/etc/tedge/operations/c8y")))
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.518449366Z DEBUG MQTT: recv Ok(Some(Message { topic: Topic { name: "te/device/main///cmd/software_list/c8y-mapper-2024-01-20T21:09:38.518122275Z" }, payload: "{"status":"init"}", qos: AtLeastOnce, retain: true }))
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.518540296Z DEBUG rumqttc::state: Publish. Topic = c8y/s/us, Pkid = 23, Payload Size = 146
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.518631857Z  WARN c8y_api::smartrest::operations: Ignoring custom operation definition as the filename uses an invalid character. Only [A-Za-z0-9_] characters are accepted. file=/etc/tedge/operations/firmware_update.toml
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.518653395Z DEBUG rumqttc::state: Publish. Topic = te/device/main///cmd/software_list/c8y-mapper-2024-01-20T21:09:38.518122275Z, Pkid = 24, Payload Size = 17
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.518753529Z  WARN c8y_api::smartrest::operations: Ignoring custom operation definition as the filename uses an invalid character. Only [A-Za-z0-9_] characters are accepted. file=/etc/tedge/operations/firmware_update.toml
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.518798921Z DEBUG C8yMapper => Mqtt: send Message { topic: Topic { name: "c8y/s/us/operations" }, payload: "114,""", qos: AtLeastOnce, retain: false }
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.518853238Z DEBUG MQTT: recv Ok(Some(Message { topic: Topic { name: "c8y/s/us/operations" }, payload: "114,""", qos: AtLeastOnce, retain: false }))
Jan 20 21:09:38 rpi4-d83add90fe56 tedge-mapper[1279]: 2024-01-20T21:09:38.518913982Z DEBUG rumqttc::state: Publish. Topic = c8y/s/us/operations, Pkid = 25, Payload Size = 6

The simplest way to reproduce the issue of the operations directory as a child device, is to touch that directory
$ touch /etc/tedge/operations/c8y

Leads to:
$ tedge mqtt sub 'c8y/#'

[c8y/s/us/operations] 114,""

Setting the breakpoint at notify.rs:88, after connecting, I see notify::event::MetadataKind::Any events being triggered for /etc/tedge/operations/c8y very regularly. Periodically running stat /etc/tedge/operations/c8y/ I see that Change timestamp is being updated precisely every 5 seconds. This event is then simplified to FsEvent::Modify which triggers the handler that assumes Modify means new file is being created. I'll try to find out which process changes the metadata, because I can hit this bug on my dev container, but I can't reproduce it in the integration test.

This has been solved by https://github.com/Bravo555/thin-edge.io/commit/e96bad7e74f25005bd4a6516308b014f02dc6fac.

Creating a workflow.toml file doesn't lead to weird error messages related to c8y operations.
Touching /etc/tedge/operations/c8y/ doesn't create an unexpected child device named operations.

QA has thoroughly checked the feature and here are the results:

[ ] Test for ticket exists in the test suite.
[x] QA has tested the function and it's functioning according description.


DMC Log Sharing & Go Live

Value Statement #1
As DMC business owner and tech team
I want to review the logs of my "You have new information" notification in research mode
So that I can determine if the notification will go to who I intend it too and I am pleased with the margins
Value Statement #2
As DMC business owner and tech team
I want to toggle my notification from research mode to live
So that I can send notifications to Veterans
Acceptance Criteria for Value Statement #1
GIVEN  the DMC Business & Tech Team have stated their trigger has been fixed
WHEN the triggers for the "You have new information" notification are being triggered
THEN the VANotify team will provide daily logs to the DMC Tech and Business Team
Acceptance Criteria for Value Statement #2
GIVEN the logs have been reviewed by the DMC Business & Tech Team
WHEN they aforementioned give their approval to go live with the notification via email
THEN the "You have new information" notification will be toggled from research mode to live
Checklist

[ ] Share logs with the DMC daily - see example below
[ ] Upon business line approval toggle service out of research mode into live
[ ] Review attached checklist

Assumptions

We are currently waiting on the DMC Tech Team to complete their work

Additional Info/Resources
https://docs.google.com/document/d/1G_hxwRRz2FLMaSc4avgl9-fy-VRrn9L6urTSA3vmcbs/edit
Example Reporting:
Below are stats from today's batch (sent at 1/22/2021 6:40 PM CST):
Total requests from DMC: 11521
Records not found in MPI: 198
Records marked as deceased in MPI: 1280
Records without VA Profile ID in MPI: 565
No email in VA Profile: 2241
VA Profile records not found: 7 (No ContactInformationBio for VA Profile ID retrieved from MPI)
Successful email retrieval: 7230
The success rate was: 63% (7230/11521)
Out of Scope

Open Questions

Total requests from DMC: 878
Records not found in MPI:
Records marked as deceased in MPI:
Records without VA Profile ID in MPI:
No email in VA Profile:
VA Profile records not found:
Successful email retrieval:
The success rate was:

@miabecker The stats are ready! See comment above^^

Statistics for 4/14/2021:
Total requests from DMC: 901
Records not found in MPI: 72
Records marked as deceased in MPI: 1
Records without VA Profile ID in MPI: 126
No email in VA Profile: 117
VA Profile records not found: 1
Successful email retrieval: 584
The success rate was: 64.82% (584/901)
@miabecker do you want to send the stats?

Yes I'll send now!
On Thu, Apr 15, 2021 at 10:38 AM Filip Fafara @.***>
wrote:

Statistics for 4/14/2021:
Total requests from DMC: 901
Records not found in MPI: 72
Records marked as deceased in MPI: 1
Records without VA Profile ID in MPI: 126
No email in VA Profile: 117
VA Profile records not found: 1
Successful email retrieval: 584
The success rate was: 64.82% (584/901)
@miabecker https://github.com/miabecker do you want to send the stats?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/department-of-veterans-affairs/notification-api/issues/410#issuecomment-820478987,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARTMDO3K7GTQOHBZCNKDHC3TI326NANCNFSM42OZG5TA
.

--
Maria Becker
Product Manager
Email @.***
Telephone<PHONE_NUMBER>
Pronouns they/them or she/her
[image: ThoughtWorks]
http://www.thoughtworks.com/?utm_campaign=maria-becker-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator


[gsquery.py] Its pretty flippin' broken on Slackware

@Xylemon Reported the following issue with Slackware. https://github.com/dgibbs64/linuxgameservers/issues/157#issuecomment-66201954
The python Game Query function is also broken, thinking that my server is down and restarts it (which is NOT good!)
What happens with Team Fortress Classic:
bash $ tfcserver monitor
./tfcserver.sh: line 142: ip: command not found
./tfcserver.sh: line 143: ip: command not found
[  OK  ] Monitoring tfc-server: Checking session: OK
[ FAIL ] Monitoring tfc-server: Querying port: :27045: ERROR: No port supplied.
[ FAIL ] Monitoring tfc-server: Querying port: :27045: ERROR: No port supplied.
tail: cannot open '<path to>/log/console/tfc-server-console.log' for reading: No such file or directory
[ INFO ] Sent email notification to <email here>
[  OK  ] Stopping tfc-server: Chuck Bronson's Prestige and Well-Mannered Debate Lounge [BETA]
./tfcserver.sh: line 142: ip: command not found
./tfcserver.sh: line 143: ip: command not found
[  OK  ] Starting tfc-server: Chuck Bronson's Prestige and Well-Mannered Debate Lounge [BETA]

Slackware comes with Python 2.7.5 by default, so I don't think that's the issue there.

Dont know if this was ever resolved however closing.


Write a C++ program to convert string to snakecase

Description
Write a C++ program to convert string to snakecase
Snakecase is a style of writing in which all letters are lowercase and spaces are replaced with underscores.
Input  : "hello world"
Output : "hello_world"

How to contribute

Save the solution in program/ConvertStringToSnakecase.cpp file
Add ConvertStringToSnakecase.cpp file in convert-string-to-snakecase folder

!assign


refactor: align workflows, guidelines and documentation structure with connector repo

What this PR changes/adds

Adds PR validation (enforce conventional commits on main)
Adds issue templates
Removes duplicated contribution files and references the connector repo
Adds toc of decision records (list will be shown via GitHub pages)

Why it does that
Align with main repo, prepare for external documentation framework, improve community contributions
Further notes
--
Linked Issue(s)
Closes # <-- insert Issue number if one exists
Checklist

[ ] added appropriate tests?
[ ] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?
[ ] added relevant details to the changelog? (skip with label no-changelog)
[ ] formatted title correctly?

Ideally the pipeline should be green as well for PRs opened from within the eclipse organization. I assume the federated credentials have not been correctly setup for PRs (for "main" they must have as they seem to work properly). Here are the instructions how to set them up: https://github.com/eclipse-dataspaceconnector/MinimumViableDataspace/blob/main/docs/developer/continuous-deployment/continuous_deployment.md#configure-pull-request-credentials

Ideally the pipeline should be green as well for PRs opened from within the eclipse organization. I assume the federated credentials have not been correctly setup for PRs (for "main" they must have as they seem to work properly). Here are the instructions how to set them up: https://github.com/eclipse-dataspaceconnector/MinimumViableDataspace/blob/main/docs/developer/continuous-deployment/continuous_deployment.md#configure-pull-request-credentials

Approving PR to unblock as it does not contain any code changes. Pipelines are probably failing due to the aforementioned missing configuration, which can be solved separately.


HTTP health check

Hi,
Is there a way to do a basic health check of a node with http request?
Something like GET /healthcheck that returns 200 if node is up, and does not require api key.

The default /metrics endpoint works without authentication, just make sure to configure the firewall properly.

It works, awesome.
Worth mentioning that the default port is 8888.
Thanks


FABButton nor any other Buttons work

i did the following:
import 'react-mdl/extra/material'
import 'react-mdl/extra/material.css'
import { FABButton, Icon } from 'react-mdl'

and then
    <FABButton
      colored = {true}
      raised = {true} >
      <Icon name={'hello'} />
    </FABButton>

I get the following result:

I was expecting this:

Hmm.. Just tried on codepen and everything seems ok: http://codepen.io/anon/pen/VjmNad?editors=001
Make sure the styles are loaded properly in your setup

@tleunen  it seems to work with cdn link so is this import statement incorrect?
import 'react-mdl/extra/material.css'```

also is it possible to change color of this button?

Your imports look ok. Maybe the issue is inside your css loader?

Is this working for you now @jasan-s ?


Initial Schedule Changes

I have more radical ideas to come but will save those if we need more space. The more obvious and conservative changes represented by this pull request include:

Added back room 4 to Friday.
Added in non-science workshops to help calculate space. Not all of them get exactly 3 hours because there is just not enough periods of unbroken space to do that.
Let some workshops run over a little into the 2 hour lunch (which can actually help stagger delegates)

To see the current number of free talk slots, you can use:
cat schedule.rst | grep -o XTalk | wc -l

This currently gives 67. This does not include science track talks.

Good work that @zeth.
I'm running out of steam to look at this properly tonight, but everybody with an interest should make sure they find at least ten minutes tomorrow to look over this and think through any potential problems.
My only observation is that it's too early to start putting workshops into slots: firstly, I'm quite keen that we don't take at least one of those workshops (I think it had a very weak proposal, the proposer hasn't responded to my feedback, and the proposer has submitted several talks that I think we should prefer) and secondly, we don't yet know that the workshoppers will be able to give their workshop on the days that we've allocated.
Apart from that -- great stuff.  Go and have a drink!

My only observation is that it's too early to start putting workshops into slots:

Fair enough. As they are such a massive allocation of time and have such massive side-effects on the placement of everything else, could you perhaps please review the workshops first?
firstly, I'm quite keen that we don't take at least one of those workshops
Perversely, from my perspective that is great news, every workshop takes up 5-6 talks worth of space so reject away :)

Workshop names are now removed and the placeholder XWorkshop is in place.
cat schedule.rst | grep -o XWorkshop | wc -l
6

This is great work @zeth - kudos to you.
A couple of points spring immediately to mind:

There will be a huge amount of equipment (think Raspberry Pis, Monitors, robots, general stuff) and probably a lot of kid-related mess that'll need putting away post-kids' day. Sticking a workshop right after it is basically impossible. It took us at least an hour to put everything away last year.
The kids' lightning talks - there will be huge logistical cat-herding exercise getting the kids and their parents over to the main hall to start at 3:30pm. There will need to be enough room in the hall for the kids and parents. I also notice there's a keynote right up until the 3:30 slot. I estimate it'll take at least 15 minutes to get kids/parents over and sat down. Perhaps the keynote can be 45mins..?

This latter problem has only just occurred to me. I believe giving the kids an opportunity to lightning talk to the conference is a brilliant thing to do. However, the logistics of this give me the collywobbles. Suggestions on a postcard please!

Not sure this is the best thread but I want to remind people for last
minute changes due to illness, or whatever reason, I can have SMS schedule
updates sent out. So we shouldn't worry excessively about changes, we are
programmers. We aren't incapable of smooth updates all of the time :)
Are we capturing numbers yet?
I did ask Ntol about an account in the new ticket system. I'm going to use
Twillio.


[BUG] ...Tookit does not appear to be working

Bitwarden "forgot" my YNAB password and I had to reset it. Today, none of the Toolkit settings are being applied to my YNAB. I don't know if it a coincidence.
I changed various Toolkit settings but nothing changes in YNAB. I closed Bing, refreshed the YNAB page, no changes to YNAB. I restarted Bing, no change. I tried Chrome, I changed sever settings, refreshed the browser, no changes in YNAB. I restarted Chrome, no changes in YNAB.

Duplicate of #3067, and should already be fixed (from what I’ve seen).

@mavwitt You might get better assistance by providing more information instead of being dismissive. :)
The symptoms you describe are exactly the same as what other people have been experiencing, which is why this probably is a duplicate of an already-fixed issue. The issues are a result of YNAB moving from app.youneedabudget.com to app.ynab.com.
If you go to your "Manage extensions" page and go to the details of the YNAB extension, what version are you running?
Mine showed version 3.5.0, and app.ynab.com doesn't work with that version.
Once you update to 3.6.0, you have to re-enable it, and reauthorize it:

Then the Toolkit for YNAB extension should work again, with the same settings that were saved from before.

Mine was updated and other then the "Emphasize Available to Assign" the toolkit was working again after the update. This morning I opened chrome and the toolkit was disabled in chrome extensions so I re-enabled it but now I am back to the toolkit not working at all in ynab with version 3.6.0.

Thanks @axenstarr . I am glad to know I am not the only one experiencing this issue.

Observation: I changed my YNAB password. Is that a prerequisite to the fault?

Ok so I fixed mine. After I re-eanbled the extension from it being disabled I closed out chrome and my 50000 tabs and then relaunched it and now everything is back working with the toolkit with the exception of "Emphasize Available to Assign".

I disable the extension, closed all browsers, restarted the computer, re-enabled the extension. No change. The problem still existed.  I deleted the extension, re-installed it, now it is working but it is back to version 3.5. It looks like version 3.6 got pulled back.

I think I spoke too soon. I am making changes in V3.5 but YNAB is not changing when I refresh my screen. I guess I will wait until I hear the "All clear".

3.6 is still available.

Looks like 3.6 is available on Chrome but 3.5 is available on Edge.

I have the same issue.  Toolkit 3.6, tried removing and reinstalling the toolkit to no effect.  Appreciate any help.

It looks as if this repair is still in progress. Everything is working for me since I updated toolkit to3.6 except for the referral banner (and the alternate row colors in transactions, but that hasn't worked for me since it was first reported months ago).

I work in Firefox and the Toolkit hasn't been working for 2 days.  The current version is 3.5.0.  I have Firefox set to automatically update the Tookit.  I also asked Firefox to check for updates, and it shows no updates available.

Go to Extensions in Firefox, open Toolkit and look at the version. It should be 3.6.0. If it isn't, click on "Check For Updates" at the top next to the Settings icon (looks like a gear).
If it says no updates available and your version is 3.5.0, there is something wrong. Perhaps removing Toolkit and reinstalling will fix it. There are a number of problems with either 3.6.0 or the latest YNAB (or both)

Firefox Fix to move from version 3.5 to 3.6:
Thanks Woonboats!
Took screen shots of my Toolkit Preferences.
Deleted Toolkit from Firefox.
Signed out of Firefox.
Signed back into Firefox.
Added Toolkit to Firefox and got version 3.6
Turned Toolkit on.
Signed out of Firefox again.
Signed back into Firefox.
Signed into YNAB
Toolkit working (haven't checked all functionality, but parts I did check are working)

Hey e3,
Can you check to see if the Emphasize Available to Assign is working?
Should change the available to assign to yellow and not the default green.
It's not working for me or others since before the update and after.
Thanks,
Scott
On Thu, Mar 30, 2023 at 9:22 AM e3lsntle @.***> wrote:

Firefox Fix to move from version 3.5 to 3.6:
Thanks Woonboats!
Took screen shots of my Toolkit Preferences.
Deleted Toolkit from Firefox.
Signed out of Firefox.
Signed back into Firefox.
Added Toolkit to Firefox and got version 3.6
Turned Toolkit on.
Signed out of Firefox again.
Signed back into Firefox.
Signed into YNAB
Toolkit working (haven't checked all functionality, but parts I did check
are working)
—
Reply to this email directly, view it on GitHub
https://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/3077#issuecomment-1490583278,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGR3TQH5O2AAIBJAGQ3GEUTW6WXLHANCNFSM6AAAAAAWL47PZU
.
You are receiving this because you were mentioned.Message ID:
@.***>

It looks as if this repair is still in progress. Everything is working for me since I updated toolkit to3.6 except for the referral banner (and the alternate row colors in transactions, but that hasn't worked for me since it was first reported months ago).

I've noticed that alternating row colors work, but it is only two shades of grey, not the selected colors.

Nope. All fine, thanks.
Sent with Proton Mail secure email.
------- Original Message -------
On Tuesday, June 6th, 2023 at 8:02 PM, Mike Melton @.***> wrote:

@.***(https://github.com/mavwitt) Are you still experiencing issues since upgrading to version 3.6?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Mine hasn't worked properly since upgrade to 3.6. The extension details in
firefox say I have 3.6 and there are now newer upgrades.
On Tue, Jun 6, 2023 at 6:33 PM e3lsntle @.***> wrote:

Nope. All fine, thanks.
Sent with Proton Mail secure email.
------- Original Message -------
On Tuesday, June 6th, 2023 at 8:02 PM, Mike Melton @.***> wrote:

@.***(https://github.com/mavwitt) Are you still experiencing
issues since upgrading to version 3.6?
—
Reply to this email directly, view it on GitHub,
or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/3077#issuecomment-1579653305,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZUWAXT3GE2R2SZR4DLYJTXJ7D7BANCNFSM6AAAAAAWL47PZU
.
You are receiving this because you commented.Message ID:
@.***>

@michaelcmelton I had given up. At your prompting I went into the Toolkit and found it was working properly. I was able to change about a dozen settings. Thanks for checking in. I will close this thread now. Hope others are finding it works for them as well.

@woodnboats Please open a new issue and fill out the template as closely and completely as possible to assist us with proper triaging and expediting a solution to your issue.

Still don't work


Add collapsible install sections

Current dependencies on/for this PR:

main

PR #163   👈

This stack of pull requests is managed by Graphite.