docker unit override removes the --containerd flag

Not sure if it is required. We aren't running with it now. The comment in the main unit file isn't clear. Investigate.

The text in the unit file is:
# the default is not to use systemd for cgroups because the delegate issues still
# exists and systemd currently does not support the cgroup feature set required
# for containers run by docker
ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

However, removing --containerd is a no-op, because docker-ce installs and uses containerd not systemd by default so removing the flag is fine. I think it's there for documentation only.


WIP: Optimize instruction encoding

This experimental PR implements space-optimized instruction encoding. So far we use a Vec<Instruction> to represent the instructions of all Wasm functions where Instruction is a simple Rust enum with size_of<Instruction>() = 16. So every wasmi instruction takes up exactly 16 bytes of memory. Of course there are many instructions such as i32.add that could theoretically reside in a single byte representing its opcode which would save us 15 bytes.
This PR tries to mitigate this issue by efficiently encoding all wasmi instructions into a Vec<u8> so that encoded Instruction only consume the amount of space they really need. This means that with this PR all encoded wasmi instruction will require a different amount of space. Depending on our decisions even the same wasmi instruction might require a different amount of bytes for its representation. For example a br_table might store its targets inline. We have not yet decided upon this though.
The downside is that this will incorporate even more unsafe code into the engine parts of wasmi which is obviously something we rather want to avoid.

The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #710      +/-   ##
==========================================
- Coverage   79.87%   79.52%   -0.36%
==========================================
  Files         101      102       +1
  Lines        8479     8517      +38
==========================================
  Hits         6773     6773
- Misses       1706     1744      +38

Impacted Files
Coverage Δ

...ates/wasmi/src/engine/func_builder/inst_encoder.rs
0.00% <0.00%> (ø)

crates/wasmi/src/engine/func_builder/mod.rs
91.66% <ø> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Closed in favor of https://github.com/paritytech/wasmi/pull/716.


Can't find source for Cloud Foundry CLI Plugin

I wanted to learn more about this plugin in order to perhaps find either the reason for another issue or at least learn something.
But unfortunately I did not find the go sourcecode although I even downloaded the whole project and searched offline. Is the plugin part of the pommercial part of pcf dev and closed source ?

Hi @mar1ged,
The source code for the CLI plugin will be released soon. We're currently adding support for running OSS builds of PCF Dev using the plugin, and we plan to open source it as soon as we get that working.
Thanks,
Stephen

Thanks a lot, now I know that I was not blind ;-)


silx: Uses old name of sip module

Hello, guyes,
I am preparing the 0.13.1. version for Debian/Ubuntu/...
I got this bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966051
cheers
Fred

That import only takes places if PyQt5 cannot be imported. If PyQt4 is dropped it is not needed.
Is that bug report an "automatic" finding or somebody has actually fallen into that "leftover"?

Please note that if one uses PyQt4 the correct import is "import sip" and obviously not "import PyQt5.sip"

Hi,
Double checking it, import sip should not occur if PyQt5 is available.
Nothing we can do until we drop PyQt4 support (already deprecated for a year).
I'm closing it, please reopen if needed.


[bazel] Update the binary/test rules for building ROMs

Add a kind attribute to the binary and test rules to indicate
whether the target is for flash, ram or rom.
Plumb flash scrambling support into the exec_env and binary rules.
Update the rom attribute in the exec environments and binary rules.
Allow the label to be any provider.
Implement flash and rom paths for fpga_cw310 and sim_{dv,verilator}.
4a. When building, apply the scrambling transform to the ROM binary.
4b. When testing, retrieve the supplied ROM and substitute it into the
test flow.  Currently, only verilator can run ROM tests.
Build the test_rom with the new rules.
Update the rom_epmp_test to the new rules.

This PR depends on #19650 and #19697.  You need only review the last 3 commits.

The commits in this PR were merged as part of #19719.


[build] compilation warnings

Issue description
Compilation warnings that could be fixed.
Environment
emscripten, Debian 11.
But can be reproduced with extra compilation flags: -Wunused-but-set-variable -Wunused-function -Wimplicit-const-int-float-conversion
Code Example
 In file included from rcore.c:101:
./rlgl.h:3025:9: warning: variable 'mipOffset' set but not used [-Wunused-but-set-variable]
 3025 |     int mipOffset = 0;          // Mipmap data offset, only used for tracelog
      |         ^
In file included from rcore.c:489:
./platforms/rcore_web.c:1006:13: warning: unused function 'WindowMaximizeCallback' [-Wunused-function]
 1006 | static void WindowMaximizeCallback(GLFWwindow *window, int maximized)
      |             ^~~~~~~~~~~~~~~~~~~~~~
./platforms/rcore_web.c:1178:16: warning: unused function 'EmscriptenWindowResizedCallback' [-Wunused-function]
 1178 | static EM_BOOL EmscriptenWindowResizedCallback(int eventType, const EmscriptenUiEvent *event, void *userData)
      |                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
emcc -c rtextures.c -Wall -D_GNU_SOURCE -DPLATFORM_WEB -DGRAPHICS_API_OPENGL_ES2 -Wno-missing-braces -Werror=pointer-arith -fno-strict-aliasing  -std=gnu99 -fPIC -Os -I.  -Iexternal/glfw/include -Iexternal/glfw/deps/mingw
In file included from rtextures.c:216:
./external/stb_image_resize2.h:2866:14: warning: unused function 'stbir__support_zero' [-Wunused-function]
 2866 | static float stbir__support_zero(float s, void * user_data)
      |              ^~~~~~~~~~~~~~~~~~~
3 warnings generated.
emcc -c rtext.c -Wall -D_GNU_SOURCE -DPLATFORM_WEB -DGRAPHICS_API_OPENGL_ES2 -Wno-missing-braces -Werror=pointer-arith -fno-strict-aliasing  -std=gnu99 -fPIC -Os -I.  -Iexternal/glfw/include -Iexternal/glfw/deps/mingw
emcc -c utils.c -Wall -D_GNU_SOURCE -DPLATFORM_WEB -DGRAPHICS_API_OPENGL_ES2 -Wno-missing-braces -Werror=pointer-arith -fno-strict-aliasing  -std=gnu99 -fPIC -Os -I.  -Iexternal/glfw/include -Iexternal/glfw/deps/mingw
emcc -c rmodels.c -Wall -D_GNU_SOURCE -DPLATFORM_WEB -DGRAPHICS_API_OPENGL_ES2 -Wno-missing-braces -Werror=pointer-arith -fno-strict-aliasing  -std=gnu99 -fPIC -Os -I.  -Iexternal/glfw/include -Iexternal/glfw/deps/mingw
In file included from rmodels.c:111:
./external/par_shapes.h:1133:32: warning: implicit conversion from 'int' to 'float' changes value from<PHONE_NUMBER> to<PHONE_NUMBER> [-Wimplicit-const-int-float-conversion]
 1133 |     float r = (float) rand() / RAND_MAX;
      |                              ~ ^~~~~~~~
/home/runner/work/_temp/347782bb-feec-47ed-8688-38a6103a1214/emsdk-main/upstream/emscripten/cache/sysroot/include/stdlib.h:84:19: note: expanded from macro 'RAND_MAX'
   84 | #define RAND_MAX (0x7fffffff)
      |                   ^~~~~~~~~~
1 warning generated.

@Lecrapouille There is only one of those warnings that atually can be reviewed.

mipOffset is actually being used, compilation fails if not defined.
WindowMaximizeCallback() can be commented, a PR is being sent.
EmscriptenWindowResizedCallback(), there is an open PR that could require it #3520
All the other ones belong to external libraries, not raylib, and they should be addressed in respective repos.


Issue 180. Updating sphinx requirements.txt

Description

Update Sphinx dependencies to the latest version and the same version as other ReDATA repositories, because the latest versions are maintained and previous versions may not be maintained (i.e. issues, security patches).

See https://github.com/UAL-RE/ReQUIAM/issues/180
ToDo List

[x] Check https://requiam.readthedocs.io/
[x] Check RTD build status at https://readthedocs.org/projects/requiam/builds/

Test plan

see the above
Resources

RTD configuration file https://docs.readthedocs.io/en/stable/config-file/v2.html
Screenshots or additional context

I have update ReQUIAM's sphinx the same structure (almost the same setting) as that of redata-commons. The goal is to have easier and consistent maintenance.

Sounds good!


Add authentication and Login Screen.

https://github.com/jayzamazing/Restaurant-POS/pull/18 fixes this issue.


added Avatar component

Is something prevents merging?

@goodmind Not really, I will take care of it soon 😅


NPT-644 Add support to upgrade nexus DM using compiler

Nexus node spec updates made by users may result in backward incompatibility. User should be able to upgrade datamodel based on the force flag and observe the incompatible changes
This PR calls common-library to see if the old and new crd have undergone any modifications, and if there have been any incompatible changes

Compiler should iterate through all created datamodel objects to ensure backward compatibility
If there are incompatible modifications and the force flag is enabled, the message notice will be logged in the console
If the force flag is deactivated and there are incompatible changes, the operation should fail with incompatible errors

JIRA: https://jira.eng.vmware.com/browse/NPT-644
Design:  https://miro.com/app/board/uXjVOM8wPKU=/?moveToWidget=3458764537971146485&cot=14


ReferenceError: require is not defined

at file:///C:/Users/Lenovo/AppData/Roaming/npm/node_modules/appstore-connect-jwt-generator-cli/bin/cli.js:2:1
at ModuleJob.run (internal/modules/esm/module_job.js:152:23)
at async Loader.import (internal/modules/esm/loader.js:166:24)
at async Object.loadESM (internal/process/esm_loader.js:68:5)

@DreamPWJ
Thanks for the report. I will look into the cause of this problem.

@DreamPWJ
Fix the this problems.
Please update the version to 1.0.2.


Not making it to run the code for images (Request!)

Hello! Thank you so much for the work and providing codes.
I am new to this field. I tried the code on Google Colab following the pattern you have provided, but my efforts went in vain (Mainly, the dataloader.). I would be very thankful if you provide any notebook for any of the image dataset.
Regards

Or any guidance in this regard would be much appreciated, sir.

Hi! To run code on image datasets I would recommend looking at the experiments_img.py file. This contains code to run experiments on image datasets. It should be pretty easy to take this code and port it to a notebook 😄
Hope that helps!

Hi! To run code on image datasets I would recommend looking at the experiments_img.py file. This contains code to run experiments on image datasets. It should be pretty easy to take this code and port it to a notebook 😄
Hope that helps!

Hi! Thank you so much for the response, sir!

Hi, sir! I want to test on brain MRI data set. What would you suggest in this regard? Would be very much thankful!

Hi, if you want to test on brain MRI data, I would suggest trying to build a dataloader for this dataset that looks exactly like the ones for MNIST or CIFAR10, i.e. each dataset item should return a tuple of an image (as a tensor) and a label (as an int). If you put this dataloader in the dataloaders.py file you can then import it at the top of experiments_img.py. You should then simply add a few extra lines here with something like
if dataset == 'brain_mri':
  data_loader, test_loader = brain_mri_dataloader(training_config["batch_size"])
  img_size = (1, 32, 32)  # Put your image sizes here
  output_dim = 10  # Put your number of classes here

Good luck!

Hi, if you want to test on brain MRI data, I would suggest trying to build a dataloader for this dataset that looks exactly like the ones for MNIST or CIFAR10, i.e. each dataset item should return a tuple of an image (as a tensor) and a label (as an int). If you put this dataloader in the dataloaders.py file you can then import it at the top of experiments_img.py. You should then simply add a few extra lines here with something like
if dataset == 'brain_mri':
  data_loader, test_loader = brain_mri_dataloader(training_config["batch_size"])
  img_size = (1, 32, 32)  # Put your image sizes here
  output_dim = 10  # Put your number of classes here

Good luck!

Thank you so much, sir!


[Bug]:

Contact Details
<EMAIL_ADDRESS>What happened?
I was using /api/IOntologyAPIv2/getAllTermsByChildTerm (with "Name": "tropical mangrove" and "TermAccession": "ENVO:01000403") and among the results (see the attached file) I could see three of our own terms referenced with NFDI4PSO (e.g. NFDI4PSO:0002008) instead of the DPBO terms. What database is the API accessing that these terms are still being returned? That shouldn't be possible anymore. Since we want to work with the DataPLANT ontology service this issue is quite important to us since we need to know the relationships of terms inside the database.
response_1707896805244.json
What did you expect?
At the most, I expected DPBO terms instead of NFDI4PSO terms (in addition to all other retrieved entries), if they were still linked to my query term the same way (which I don't believe they are, going by the related term search in Swate). One of the results is "environment (feature)" (NFDI4PSO:0002008). This term also exists in DPBO (DPBO:0002008), but there are no child terms linked (as opposed to the NFDI4PSO term), since it shows no children in the tree view and also doesn't return any children using the API /api/IOntologyAPIv2/getAllTermsByParentTerm.
Host
Excel
Host Details
Web Version Excel, Ubuntu 22.04 LTS
Swate version
Ontology DB Api - v2   0.0.1   OAS3; Swate v1.1.0-alpha.10

Hello! It uses the database setup from Swobup. I already contacted marcel to remove the nfdi4pso from the database and he updated swobup to not read in the nfdi4pso again. After checking i found around 500 terms from nfdi4pso still in the database. These were now removed and should never appear again. Feel free to open another issue (reopen) if you should find another nfdi4pso term.

At the most, I expected DPBO terms instead of NFDI4PSO terms (in addition to all other retrieved entries), if they were still linked to my query term the same way (which I don't believe they are, going by the related term search in Swate). One of the results is "environment (feature)" (NFDI4PSO:0002008). This term also exists in DPBO (DPBO:0002008), but there are no child terms linked (as opposed to the NFDI4PSO term), since it shows no children in the tree view and also doesn't return any children using the API /api/IOntologyAPIv2/getAllTermsByParentTerm.

Regarding this part, i was not informed about any changes in the ontology structure, you might need to open this as a new issue in the nfdi4plants_ontology repository

Awesome, thank you for the quick fix! I'll ask Kathryn regarding the structure


Item height based on content (auto)

Good day and thanks for the super plugin!
Is it now possible and if not is it possible to add a preview item height based on the content height? Like a default html behavior? No need to guess and set pixels... I've tried set Item height to 0, but they just disappeared.

No this is not possible, the item height is always fixed, as this is required for loading and rendering the item in joplin.

Thanks for your response! Could you please lead me to the info about the need for a fixed item height? I've tried to play around with the dev tools, and it seemed ok. I couldn't test all cases for sure...

Thanks!  Just for the case when one is ok with performance penalties? Or is it mandatory to set and type checked?


Error use line number in original code using sourcemap instead of /dist code

The error logging points to the line number in the /dist code. Given that we have the sourcemap from gulp, is it possible to point to the file and line number based on the original code?

@KunalKapadia @laumair I have same question.

@mmestani I actually figured this out. I installed this npm modules: https://github.com/evanw/node-source-map-support
Follow the installation direction and the sourcemap line number issue gets solved automagically!

@mmestani Currently the boilerplate misses this functionality. @KunalKapadia maybe you need to take a look if its important to add. Otherwise, @ruler88 managed to sort it out with https://github.com/evanw/node-source-map-support.
P.S: I haven't really used this one. Seems good to me.

@ruler88 @laumair thanks, I'll try this one. for my opinion its good to have buit-in. This project looks very promising to me :)

@laumair Would you like to take this up as well ?
If not, I'll start working on this. Seems like a small one.

@KunalKapadia Apologies for the late reply. Have been really busy with stuff. Is this picked already? @mmestani

@laumair Not picked up. Please feel free to raise a PR.


COCO dataset support

POSE parameters in configs.py is with respect to AI-Challenger dataset. Any idea, what is the value of these parameters in COCO
_C.POSE.NUM_KPTS = 14
__C.POSE.NUM_PAFS = 22  # (11 * 2)
__C.POSE.KPT_THRESH = 0.1
__C.POSE.SCALE = (512, 512)
__C.POSE.LIMBS = [[1,2], [2,3],
[4,5], [5,6],
[14,1], [14,4],
[7,8], [8,9],
[10,11], [11,12],
[13,14]]
__C.POSE.HEAD = [13, 14]
__C.POSE.BODY = [[1,2], [2,3],
[4,5], [5,6],
[14,1], [14,4],
[7,8], [8,9],
[10,11], [11,12]]
__C.POSE.LIMB_WIDTH = 2.5
__C.POSE.GAUSSIAN_VAR

Please refer to COCO official annotations, I don't remember exactly.

Ok. Thanks for the simplified code. It works great. The npy dataset generation for RNN takes more time for a single video. Can you please share the generated npy dataset for Chinese Police Gesture dataset if available.

https://drive.google.com/drive/folders/1G9t3GwQrWkhb56kUSCVxyhCu6wD4BD2w?usp=sharing

Thanks a lot


[9.x] Add zero-width space to trimmed characters in TrimStrings middleware

I had a weird bug recently when adding a job to the queue when the content had a zero-width space present somewhere.
The bug I had was: Unable to JSON encode payload. Error code: 5
It took me a while to corner this issue to a zero-width space present in a user firstname.
I was wondering also if would be interesting to add a middleware to actually remove those characters also from within the fields instead of just the side. I am willing to create another pull request if that need can benefit more people.
Github does not show the diff, so here is a visual diff:
Before

After

Also, I can try and add a test for this if necessary.

Yeah we would definitely want a test for this I think.

Please mark as ready for review when it has a test.

I tried to think of multiple situations with the tests, I hope it's fine like this!

woops, I have noticed a tiny typo issue in the last test, should I open a new pull request?
The title should not be This title contains a zero-width non-breakable space at the end, it should be This title contains a combination of zero-width non-breakable space and zero-widh spaces characters at the begining and the end instead.
The test is still valid, it's just the title that does not fit the test name.

@tomcodes yes feel free to send in a new pr


Add dr_libs (dr_flac, dr_mp3 and dr_wav)

Sorry for all the errors, I am really tired. 😅

thanks.:+1:


Handle Partial Data

This is a draft pull request to handle partial data being received on the IB connection socket.
The data parsing method appears to previously have been biased to assume that each call of the event handler would have a full and complete response from the IB server. However, that does not correctly handle cases where the socket might have buffered data from multiple calls ( or any other number of scenarios where the data received is partial ) and require that prior data that was received may in fact be part of a valid-yet-not-complete send on the part of the gateway / TWS.
This PR:

Buffers data from previous calls and attempts to dispatch messages as they become fully formed
Only buffer the data that has not yet been fully read
Handle cases where the data parsing exceeds what the max message size might be, and panic ( as best possible )

My rationale for panic was that every effort should be taken to prevent a case where a physically-valid-but-logically-incorrect packet might be dispatched to a receiver.
No tests currently because I am not quite certain how the testing process is done w/ this lib. PR'ing now for review / any possible discussion.

NP - in terms of repro, for my use case, I essentially did the following:
client.reqContractDetails(...)
client.reqContractDetails(...)
client.reqContractDetails(...)

While my code did not look exactly like that ( I'm building a Promise based interface around this ), the net effects were 3 sends, one after the other, which seemed to regularly cause payloads to be broken up when talking to TWS.

Hmm.. thinking if it same issue I same randomly when I breakpoints inside the IO and stop for (>10s):
info: 22:36:53: IBPlugin: Connection status: Connected     at Socket.onData (C:\srcmfr\sauron-server\node_modules\@stoqey\ib\src\io\socket.ts:198:30)     at Socket.<anonymous> (C:\srcmfr\sauron-server\node_modules\@stoqey\ib\src\io\socket.ts:115:34)     at Socket.emit (events.js:315:20)     at addChunk (internal/streams/readable.js:309:12)     at readableAddChunk (internal/streams/readable.js:284:9)     at Socket.Readable.push (internal/streams/readable.js:223:10)     at TCP.onStreamRead (internal/stream_base_commons.js:188:23)     at TCP.callbackTrampoline (internal/async_hooks.js:131:14) [ERROR] 22:37:09 RangeError: The value of "offset" is out of range. It must be >= 0 and <= 65535. Received 65536
errors.
socket.ts:198:30 is the data.readUInt8 that reads from socket to into buffer. We try to read more we should, means we got a nonsense message size. Cloud be related to what you have just fixed. Will add the patch and and check if it still happens.

That error message definitely is what tripped me on to this problem; I saw same.

Problem with debug break is gone for mw (at least for now, was very random, but confident this is the fix for it).
Merged


Update installing-cardano-node.md MacOS update

Updating documentation
Description of the change
export PATH="~/.local/bin/:$PATH" didn't work with me on Mac OSX 11.5.2 running zsh, since my .zshrc didn't recognize ~ as $HOME. Instead, it worked with export PATH="$HOME/.local/bin/:$PATH" which I believe should work for others as well.
An alternative update to instructions could be to specify that export PATH="$HOME/.local/bin/:$PATH" could work if export PATH="~/.local/bin/:$PATH" does not.
So it saves time for anyone debugging why running cardano-cli --version doesn't work.

Duplicate of #290


Add back machines

machines-0.6.1 has been released, which has GHC 8 compatibility and working tests/benchmarks.

:+1:


Information icon in File Switcher is not themed under the dark theme

Issue Report Checklist
Originally discussed on #8068 .
Under the dark theme, the "information" icon in the file switcher is still not themed, as seen in #8616 .

Versions

Spyder version: 4.0.0 latest master
Python version: 3.7.3
Qt version: 5.9.7
PyQt version: 5.9.2
Operating System name/version: Windows 8.1 x64

Dependencies

qdarkstyle 2.6.8

@CAM-Gerlach could you tell me which widget is that button? Mays is something with qdarkstyle, maybe not. Tks

@dpizetta Thanks. The issue is with Spyder, by all appearances, but it should be pretty straightforward for them to resolve once they get to it.
In spyder/widgets/helperwidgets.py:
class HelperToolButton(QToolButton):
    """Subclasses QToolButton, to provide a simple tooltip on mousedown.
    """
    def __init__(self):
        QToolButton.__init__(self)
        self.setIcon(get_std_icon('MessageBoxInformation'))
        style = """
            QToolButton {
              border: 1px solid grey;
              padding:0px;
              border-radius: 2px;
              background-color: qlineargradient(x1: 0, y1: 0, x2: 0, y2: 1,
                  stop: 0 #f6f7fa, stop: 1 #dadbde);
            }
            """
        self.setStyleSheet(style)

Tks. The style is hardcoded. Try to remove this, then it will use the qtoolbutton style. If any problem still there, let me know.
        style = """
            QToolButton {
              border: 1px solid grey;
              padding:0px;
              border-radius: 2px;
              background-color: qlineargradient(x1: 0, y1: 0, x2: 0, y2: 1,
                  stop: 0 #f6f7fa, stop: 1 #dadbde);
            }
            """
        self.setStyleSheet(style)

Thanks @dpizetta , hopefully someone will get to this soon and your suggestion works.

Thanks @dpizetta , I'm sure the Spyder team will appreciate your help.

@dpizetta, thanks a lot for your help with this one!
@juanis2112, please take a look at this issue, following @dpizetta's advice. The idea is that the icon uses MAIN_FG_COLOR so that it looks white on the dark interface and black on the light one.


The release ZIP file needs a README.html file pointing to the web site

There is a README file already, but it isn't named README. So I've renamed the file.
I've also embellished it and the build file with an explanation of abbreviations.

Actually, the readme file was being copied to the ZIP and then being overwritten. Now it is being copied to the ZIP with a unique name.


styleguide link broken in this branch [FIXED]

Style guide link was broken , Now fixed

Thanks. This was already fixed in #247 and will be updated when master is merged into that branch.


Promise.prototype.finally() broken in Firefox

Version
3.0.0-rc.10
Node and OS info
Node 10.6.0 / Yarn 1.9.2 / macOS 10.13.5
Steps to reproduce

Clone https://github.com/mserajnik/vue-cli-promise-finally
Install with Yarn
Run with yarn serve
Open the development URL in Firefox (tested under Firefox 61.0.1)
Check the console: [Vue warn]: Error in created hook: "TypeError: this.fetchData(...).then(...).catch(...).finally is not a function"

What is expected?
According to the MDN web docs, Promise.prototype.finally() is supported natively in Firefox since 58, so it should work, even without any polyfill.
What is actually happening?
Promise.prototype.finally() does not work in Firefox (61.0.1).

Not sure if I'm missing something obvious here – I'm not even sure if this is actually a bug or just a configuration issue (maybe I have to adjust my babel.config.js in some way?). What is weird is that Promise.prototype.finally() works in Safari when I run the same test app, which doesn't have native support for it apparently – so the polyfill seems to be working there. I can only reproduce the issue in Firefox. A friend has also confirmed the same issue in Firefox under Windows 10.
Oh, and sorry if this issue belongs somewhere else. Since I couldn't pin down if it's a Firefox bug, an issue with Babel or one with the @vue/app preset (or just a configuration error on my end), it made the most sense to me to open it here first.

Hm, I remember coming across something like this a while ago when building a prototype with beta.3 or something.
We include a Promise polyfill with vue-cli by default. Maybe we have a weird situation where

The polyfill doesn't include finally
in Firefox, the polyfill is installed even though it should be skipped as FF has native Promises already

If so, 1.) would be an issue to solve in vue-cli, if 2.), which would be a problem with babel-polyfill / core.js, can't be resolved quickly.

According to this there's also es.promise.finally, which I tried to add the following way:
module.exports = {
  presets: [
    ['@vue/app', {
      polyfills: ['es6.promise', 'es6.promise.finally', 'es6.array.iterator']
    }]
  ]
}

Hoewever, this throws an error on build:
Cannot read property 'android' of undefined (While processing
<EMAIL_ADDRESS>    at targetEnvironments.filter.environment (/fake/path/vue-cli-promise-finally/node_modules/@babel/preset-env/lib/index.js:75:
16)

Doing the following seems to work:
// babel.config.js

module.exports = {
  presets: [
    ['@vue/app', { useBuiltIns: 'entry' }]
  ]
}

// src/main.js

import '@babel/polyfill'

[…]

It does increase the bundle size a bit (as expected), but that's not really an issue.
According to this comment from Brian Ng:

Yep, there's currently no usage mapping for .then, .catch or .finally.

So, issue solved for me. Do you think you could mention this limitation of having useBuiltIns in usage mode somewhere in the readme of @vue/babel-preset-app? I know that's an issue/limitation with @babel/preset-env itself, but given that @vue/cli is pretty much zero config by default and very beginner-friendly for people who haven't worked with webpack/Babel/etc. before, this is likely one of the first places they'd look if they encountered such an issue.

This is an issue in core-js - its promise polyfill replaces the native Promise in Firefox, however according to author of core-js, it is doing it because Firefox's Promise implementation somehow fails a subclassing check so is technically not spec-compliant.
For now I've included es7.promise.finally by default to fix this in Vue CLI.

@yyx990803
Thanks, I think that's a decent solution for now.
I had forgotten Promise.prototype.finally() is not part of the ES6 spec, so the way I've tried to include the polyfill before (via es6.promise.finally) obviously didn't work in hindsight. Time to switch useBuiltins back to the default usage mode. :)

@yyx990803
什么时候发布版本，这个finally配了好久都没有配置好

Sorry to comment on a closed topic but I'm getting an error relative to the subject.
`This dependency was not found:

core-js/modules/es7.promise.finally in ./src/main.js

To install it, you can run: npm install --save core-js/modules/es7.promise.finally`
I'm getting the error AFTER the rc10, so I had to fix the version in rc10.

Happens to me also after installing vue-styled-components

`This dependency was not found:

core-js/modules/es7.promise.finally in ./src/main.js
To install it, you can run: npm install --save core-js/modules/es7.promise.finally`

For the records, I add this issue but only for Axios's promises.
A local Promise.all().finally were fine.
So in our API service, instead of passing Axios's promise we created a new one, like:
async handleResponse(axiosPromise, options) {
  const newPromise = await axiosPromise.then(/**/).catch(/**/)
  return newPromise
}

@mserajnik in Which Vue cli version were this bug had Fixed ?

@ahussein3 This has been fixed in v3.0.0-rc.11 in August 2018.

I still have this issue with:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
in firefox:

Promise.resolve(42).finally(() => console.log('works'));
TypeError: Promise.resolve(...).finally is not a function[Learn More]

If I type this in the console on another website it works :(

Sorry to hear that.
If you can provide an actual reproduction of tumour your issue we could investigate.
Saying "I have this problem" doesn't allow us to do that.

I realize that but the building environment is so complex I cannot allocate time for this currently, I solved my issue by just removing finally and use catch/then.
If it helps I don't have ny es(6/7).promise.finally in my current dependencies, if I understand correctly this was the fix applied, if so how is is supposed to be included ? do I need to have it explicitely in my package.json ?

@schmurfy:
If your project was created using vue-cli and you didn‘t make any manual changes to the build setup (e.g., change the Babel config in some way it would disable the usage of the es7.promise.finally polyfill), it should work out of the box.
As for the reproducable example, see the one in my opening post. That‘s just an empty project created with vue-cli (a version before the fix).
You could go this approach as well and start isolating the issue – if a new/empty project works, try to figure out what change(s) in your project cause(s) it not to work.

If core-js is used by any of your modules (i.e. Babel), that's the cause.
This code isn't present in the current version, but core-js 3.0.1 overrides it:
var FORCED = isForced(PROMISE, function () {
 // correct subclassing with @@species support
 var promise = PromiseConstructor.resolve(1);
 var empty = function () { /* empty */ };
 var FakePromise = (promise.constructor = {})[SPECIES] = function (exec) {
   exec(empty, empty);
 };
 // unhandled rejections tracking support, NodeJS Promise without it fails @@species test
 return !((IS_NODE || typeof PromiseRejectionEvent == 'function')
   && (!IS_PURE || promise['finally'])
   && promise.then(empty) instanceof FakePromise
   // v8 6.6 (Node 10 and Chrome 66) have a bug with resolving custom thenables
   // https://bugs.chromium.org/p/chromium/issues/detail?id=830565
   // we can't detect it synchronously, so just check versions
   && v8.indexOf('6.6') !== 0
   && userAgent.indexOf('Chrome/66') === -1);
});


which

I love cash! A which command would be helpful. When I have a chance, I'd be happy to implement it. This might be a good start to it.

Sure! That would be great! Feel free to ask any questions. And don't forget to vote it up in the wiki.
https://github.com/dthree/cash/wiki/Roadmap

I'm not sure how to add stuff to the wiki page. I don't see an edit link.

Oops! I thought it defaulted to being editable. Changed it, try now.

perfect. added and thumbed. thanks!

:+1:

Going to close this with favor to the roadmap! Feel free to ask any questions.

:+1:


add InCommodities

I work there, our primary language is F#

Can confirm, I work there too :-)

@esbenbjerre @inwenis Please also consider adding a testimonial to https://fsharp.org/testimonials!


Changes to support aarch64 (64-bit ARM) and s390x (zLinux) architectures

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature
Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area driver-kmod

/area driver-ebpf

/area libscap

/area libsinsp

/area tests

/area proposals

What this PR does / why we need it:
Changes needed for Sysdig agent to support aarch64 (64-bit ARM) and s390x (zLinux) architectures.
Which issue(s) this PR fixes:

Fixes SSPROD-7548
Fixes SSPROD-6955
Special notes for your reviewer:

Remove Little-Endian byte-order assumptions in HTTP header parsing and IP address checking logic.
Extend use of existing mechanisms -- volatile variable, masking -- to allow eBPF probe to be accepted by kernel verifier
Adjust set of LUA APIs used, to allow interoperability with the different LUA versions available for the different architectures.

Does this PR introduce a user-facing change?:

Sysdig agent is now supported on 64-bit ARM Linux systems.
Sysdig agent is now supported on IBM zLinux systems.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

d43d79c Fill thread loginuid with default value -1, if /proc loginuid is unavailable
9f1174c parse other container variables in static container
f03e3c6 Track container user info and expose via user.name (#7)
f335ba4 Enhancements to initial scan of /proc, for supportability
fb8d651 Rename docker_async_instruction to docker_lookup_request
9d6076f Fix comparison of docker_lookup_requests
cc64620 Pass container_id as a const ref to docker_lookup_request ctor
0491927 Move docker_lookup_request to a separate file
7138ee4 Pass docker socket to the async engine separately for each request
337c288 Move platform-specific Docker-API code to a separate class
b041084 Remove docker_connection::build_request
434f151 Move docker_async_source to its own source file
1910a45 Pass a complete request to parse_docker_async
c1ebc13 Move most of docker::resolve to a new method
884f4ef Move common docker bits to a base class
e140eff Split Linux/Windows docker implementations
49eff79 Split docker_async_source::parse_docker into helper methods
7cfc81f Support Podman quirks in docker_async_source
4526715 Support Podman container engine
be23d36 Add a podman_owner_uid label for rootless Podman containers
305a66e Actually enable the Podman engine
78e0716 Support sinsp::restart_capture_at_filepos for fd-based captures
baef089 add presubmit
0ff04fc remove unnecessary buil;d builder option
4659dd9 Match Podman images including the tag
0e5db76 Log the socket used to contact the Docker/Podman daemon
e1fb268 SSPROD-7609, create sinsp_evt copy routine
061f51f bug/dup code removed
0eb6b7e make  sinsp_threadinfo tinfo as const in populate_cmdline
7ed202f review comments
2416743 Split the right image id for podman containers
86bdf22 Fix inverted logic when checking whether image name is the id
6be1128 Flip the parameters to startswith when comparing image ids
b6270e2 Extend the comment about running containers with image ids
5c82cee Initialize m_ptid when initializing other vars
d5cf86b Changes to support aarch64 (64-bit ARM) and s390x (zLinux) architectures

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. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jcpittman144
To complete the pull request process, please assign leogr after the PR has been reviewed.
You can assign the PR to them by writing /assign @leogr 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

Hi @jcpittman144. Thanks for your PR.
I'm waiting for a falcosecurity member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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.

Retracting this PR.
I'm trying to submit to the draios/agent-libs repo, not the falcosecurity/libs repo.


Upgrade rules_swift to 1.3.0-ish

https://github.com/bazelbuild/rules_swift/pull/940

https://github.com/bazelbuild/rules_swift/pull/945

Top hatting this now in our build

Works for us in our build

:+1: I need to change this to 1.4.0 now, then I'll merge.


dotter: fix build with rust 1.61

Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/903

It wouldn't work to just pull https://github.com/SuperCuber/dotter/commit/985ccce02fee6516b313547b298179dead8ce5bd as a patch?

Yes, it's what I did. But I'd like to also include https://github.com/SuperCuber/dotter/pull/96 since it fixes some CVEs in https://github.com/NixOS/nixpkgs/issues/141368.

@SuperSandro2000 Upstream released a new version.

Thanks!


Build error with latest Quark SOC v1.2 tool chain

Issue Description

Need the right tool chain to cross-compile Soletta image for Galileo platform and clearer instruction that whether Soletta must be built with uclibc. The instructions on the webpage https://github.com/solettaproject/soletta/wiki/Galileo-and-Galileo-Gen2-Instructions points to the older Quark SOC X1000 BSP (v1.0.1), please update to the latest BSP (v1.2).
For the v1.0.1 the SDK tool chain (http://download.intel.com/support/processors/quark/sb/quark_bsp_buildandswuserguide_329687_006.pdf) by default is uclibc, but the latest BSP (http://www.intel.com/content/dam/www/public/us/en/documents/release-notes/quark-x1000-bsp-build-sw-rel-user-guide.pdf) can output two different tool chain, for SPI image will use uclibc but DEFAULT full image will use glibc.
I tried to build with the latest toolchains (both uclibc and glibc) are hitting into the same error:
  CC   build/stage/modules/flow/gpio/gpio.o
  CC   build/stage/modules/flow/aio/aio.o
  CC   build/stage/modules/flow/converter/converter.o
  CC   build/stage/lib/common/sol-blob.o

cc1: warning: ./build/stage/include/: No such file or directory
In file included from :0:0:
/home/phoongst/mywork/soletta/src/lib/common/sol-missing.h:67:1: error: static declaration of 'memrchr' follows non-static declaration
memrchr(const void *haystack, int c, size_t n)
^
In file included from /home/phoongst/mywork/soletta/src/lib/common/sol-missing.h:64:0,
from :0:
/opt/iot-devkit/1.7.2/sysroots/i586-poky-linux/usr/include/string.h:76:14: note: previous declaration of 'memrchr' was here
extern void *memrchr (const void *__s, int __c, size_t __n)
^
make: *** [build/stage/lib/common/sol-blob.o] Error 1

I then tried to build the older tool chain based on the instruction, unfortunately it failed when building the tool chain
Running: git init
Initialized empty Git repository in /home/phoongst/mywork/quark_sdk/1.0.1/meta-clanton_v1.0.1/poky/.git/
Running: git remote add origin git://git.yoctoproject.org/poky
Running: git fetch origin --depth=3 tags/dylan-9.0.2:tags/dylan-9.0.2
remote: Counting objects: 5108, done.
remote: Compressing objects: 100% (4591/4591), done.
remote: Total 5108 (delta 332), reused 2736 (delta 206)
Receiving objects: 100% (5108/5108), 9.78 MiB | 742.00 KiB/s, done.
Resolving deltas: 100% (332/332), done.
From git://git.yoctoproject.org/poky

[new tag]         dylan-9.0.2 -> dylan-9.0.2
remote: Counting objects: 4, done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 4 (delta 0), reused 4 (delta 0)
Unpacking objects: 100% (4/4), done.
[new tag]         dylan-9.0.2.rc1 -> dylan-9.0.2.rc1
[new tag]         yocot-1.4.2 -> yocot-1.4.2
[new tag]         yocto-1.4.2 -> yocto-1.4.2
[new tag]         yocto-1.4.2.rc1 -> yocto-1.4.2.rc1
Running: git checkout -b clanton tags/dylan-9.0.2
Switched to a new branch 'clanton'
Running: git init
Initialized empty Git repository in /home/phoongst/mywork/quark_sdk/1.0.1/meta-clanton_v1.0.1/meta-intel/.git/
Running: git remote add origin git://git.yoctoproject.org/meta-intel
Running: git fetch origin --depth=3 tags/dylan-9.0.2:tags/dylan-9.0.2
remote: Counting objects: 430, done.
remote: Compressing objects: 100% (274/274), done.
remote: Total 430 (delta 90), reused 326 (delta 64)
Receiving objects: 100% (430/430), 1.47 MiB | 502.00 KiB/s, done.
Resolving deltas: 100% (90/90), done.
From git://git.yoctoproject.org/meta-intel
[new tag]         dylan-9.0.2 -> dylan-9.0.2
remote: Counting objects: 11, done.
remote: Compressing objects: 100% (11/11), done.
remote: Total 11 (delta 0), reused 11 (delta 0)
Unpacking objects: 100% (11/11), done.
[new tag]         1.4        -> 1.4
[new tag]         1.4.1.rc1  -> 1.4.1.rc1
[new tag]         1.4.final  -> 1.4.final
[new tag]         dylan-9.0.0 -> dylan-9.0.0
[new tag]         dylan-9.0.1 -> dylan-9.0.1
[new tag]         dylan-9.0.1.rc1 -> dylan-9.0.1.rc1
[new tag]         dylan-9.0.2.rc1 -> dylan-9.0.2.rc1
[new tag]         yocot-1.4.2 -> yocot-1.4.2
[new tag]         yocto-1.4.1 -> yocto-1.4.1
[new tag]         yocto-1.4.2 -> yocto-1.4.2
[new tag]         yocto-1.4.2.rc1 -> yocto-1.4.2.rc1
Running: git checkout -b clanton tags/dylan-9.0.2
Switched to a new branch 'clanton'
Running: git clone git://github.com/openembedded/meta-oe meta-oe
Cloning into 'meta-oe'...
fatal: remote error:
Repository not found.
Traceback (most recent call last):
File "setup/gitsetup.py", line 131, in
main()
File "setup/gitsetup.py", line 121, in main
run_command('git clone %s %s' % (url, workdir))
File "setup/gitsetup.py", line 65, in run_command
subprocess.check_call(command, shell=True)
File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'git clone git://github.com/openembedded/meta-oe meta-oe' returned non-zero exit status 128

Steps to reproduce

Download the Soletta source code with tag v1_beta19
Build the tool chains by referring to the documentation
Build soletta

Board information
Host OS and architecture: Ubuntu 14.04.4 LTS
Target OS and platform: Linux, Galileo Gen 2
Logs

Soletta version (top commit hash): v1_beta19 (commit 6a7bc3)

.config: http://pastebin.com/h66D9zPq

config log: http://pastebin.com/q9hTxmSf
strace.zip

make log (V = 1): http://pastebin.com/1Js18jd

make strace log (strace -ff make &> strace.log): strace.zip

Hello @lblim,
Clanton is an outdated build for Yocto, and we highly recommend the use of Ostro OS.
Ostro OS is a Yocto-based operating system for IoT devices.
Try reading this working-progress documentation here and follow the steps:
https://github.com/solettaproject/soletta/wiki/Meta-Soletta
Feel free to contact me if you have any doubt.

Hey @lblim ,
Could you run 'make distclean'  (or even 'git clean -dxf' if you dont have uncommitted code) before trying the instructions to see if the problem is solved?
If you check your config file you can see that CONFIG_CFLAGS is empty, each means that you problaby compiled Soletta for your host before trying to compile for Galileo. After the environment setup, CFLAGS have the SDK info, so you should see that on your .config but is problaby not re-generated. The suggested commands should force that.
If it works, plz let us know so we can enforce those steps in the instructions text.

I am building the Soletta on its own and not with Ostro because we have not migrated to ostro OS, Ostro OS does not have some of the ingredients of our BSP. I plan to build Soletta for Apollo Lake while waiting for my team to integrate soletta into our BSP.

Hi @mbelluzzo
I tried with make distclean and git clean -dxf with a clean checkout of soletta, tried with both uclibc and glibc toolchains, both reported same error, but this time the error is different from the previous error. I tried with the v1_beta19 and master branch.
make log = http://pastebin.com/piAkGjVw
.config = http://pastebin.com/GrYVqKwX
config.log = http://pastebin.com/bQeznQrz
strace.zip

The logs are to worry about, it's mixing with your host system, things like $PATH, $PKG_CONFIG_PATH, $PKG_CONFIG_LIBDIR must be all changed to restrict access to your SDK.
also, you're missing lots of dependencies that are useful for a proper soletta application, like libcurl for http-client, libudev for device enumeration, libsystemd to control services and system state, openssl...
Specifically about make log (http://pastebin.com/piAkGjVw) you're trying to build micro-linux platform (instead of systemd, since you lack libsystemd) and that results in a failure since your linux/reboot.h header lack the suspend value RB_SW_SUSPEND.
uCLib is a poor choice of library as it misses lots of utilities we use in our linux port, like the printf() implementation is horrible and all. When attempting to do minimal systems, use musl-libc instead.
Last but not least, when you say "Ostro does not have your BSP", that's just a matter of adding your layer and using it with a higher priority than Ostro's. Please use the new instructions at https://ostroproject.org/documentation/howtos/building-images.html#adding-a-custom-layer-in-ostro-os
Cross compiling complex software with multiple dependencies such as soletta is harder than you expect :-)

Hi @Barbieri,
Thanks for the info, there are a few things I would like to suggest for the documentation update. It seems that it is not encourage to cross compile the soletta image due to dependencies, please update the page https://github.com/solettaproject/soletta/wiki/Galileo-and-Galileo-Gen2-Instructions accordingly with the working workflow or remove teh cross compile option.
I did try the uclibc and glibc and both hit into same prb, so should be the system issue. So looks like system is a MUST have component. The instruction actually asked to use Linux micro option and also the instruction asked to unset the $PKG_CONFIG_PATH etc.
Besides that, the build requirements (https://github.com/solettaproject/soletta/wiki/Build-requirements) may need to be updated since the libcurl, libudev are required and not optional.
My team is working on integrating the meta-soletta into APL-I yocto BSP now. I shall wait for them to enable it since that I am unable to proceed with cross-compile option.
Enabling Ostro OS for APL-I is in your roadmap now, so my team will pick up from there and add on meta layers that are missing to support our customers.

Hi Lee Booi,
Indeed the instructions need to be improved, there are multiple tasks pending on that :-)
The libraries are optional, but recommended. You may drop them, but you must know what you're doing. Usually would drop those in order to save memory.
It's strange glibc misses the symbol in linux/reboot.h since that exists since kernel 2.6. Maybe you missed kernel headers in your libc?

Hi Gustavo,
I found the problem already. The GCC is v4.9.1 and the glibc is v2.19, this version actually has the definition of RB_SW_SUSPEND. RB_SW_SUSPEND is defined in sys/reboot.h and it is only added after v2.16 (2012 May). However, the sysroots of the SDK somehow has the older glibc header files. Therefore is a mismatch on the glibc header files version. I am not sure why this discrepancy happen yet, I will talk to quark team on that.
commit 1a09dc565db1da971ade18d9be7d9ac82646d599
Author: Andreas Jaeger<EMAIL_ADDRESS>Date:   Wed May 23 20:16:00 2012 +0200
Add more constants to Linux <sys/reboot.h>

2012-05-23  Andreas Jaeger<EMAIL_ADDRESS>        Maximilian Attems<EMAIL_ADDRESS>
    * sysdeps/unix/sysv/linux/sys/reboot.h (RB_SW_SUSPEND,
    RB_KEXEC):
    New macros.

ok... this is the reason why Ostro exists, the previous SDK for Galileo and Edison were painful to use, weird choice of components and can't scale to add more components (the traditional YP SDK is just the compiler, while the new eSDK embeds bitbake/devtool, then allow to add more recipes)

I got the workaround for the toolchain already
Option 1 - Use the build environment SDK (created using "bitbake meta-ide-support")
Option 2 - If an SDK installer script is required (to install an SDK to a different computer) then make this simple change to meta/lib/oe/manifest.py and create the installer script again: Move PKG_TYPE_MULTILIB from last to first in the INSTALL_ORDER.
Before
INSTALL_ORDER = [
PKG_TYPE_LANGUAGE,
PKG_TYPE_MUST_INSTALL,
PKG_TYPE_ATTEMPT_ONLY,
PKG_TYPE_MULTILIB
]
After
INSTALL_ORDER = [
PKG_TYPE_MULTILIB,
PKG_TYPE_LANGUAGE,
PKG_TYPE_MUST_INSTALL,
PKG_TYPE_ATTEMPT_ONLY
]
However, I hit into another issue as below:
  CC   build/stage/modules/flow/console/console.o
  CC   build/stage/modules/flow/byte/byte.o
  CC   build/stage/modules/flow/led-7seg/led-7seg.o
  LD   build/soletta_sysroot/usr/lib/libsoletta.so

./src/lib/comms/sol-oic-server.c: In function 'res_payload_do.isra.0':
./src/lib/comms/sol-oic-server.c:239:1: internal compiler error: in propagate_rhs_into_lhs, at tree-ssa-dom.c:2913
res_payload_do(CborEncoder *encoder,
^
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html for instructions.
lto-wrapper: i586-poky-linux-gcc returned 1 exit status
/opt/quark_sdk/1.7.2/sysroots/i586-pokysdk-linux/usr/bin/i586-poky-linux/../../libexec/i586-poky-linux/gcc/i586-poky-linux/4.9.1/ld: lto-wrapper failed
collect2: error: ld returned 1 exit status
make: *** [build/soletta_sysroot/usr/lib/libsoletta.so] Error 1
Any idea?

Maybe you can try to remove -ftlo usage. Not sure if we have a way to do it now, @dorileo do you know?
This GCC 4.9 is ancient, LTO was just seeing its first users... much improved in 5.x series.

please run make with V=1 and show us the output, -flto will only be used if building with -O[0-5].

actually the other way around, -flto will only be used if not building with -O[0-5]

strange, usually LTO is used with optimizations... are you sure about that?
Anyway, try the DEBUG build, AFAIR it doesn't include the LTO

@barbieri you're right, misread in the second run :(
ifneq (,$(shell echo $(COMMON_CFLAGS) | grep -e "-O[s12345\ ]"))

.config : http://pastebin.com/4pGmTspJ
config.log : http://pastebin.com/1rBsEw7T
make log : http://pastebin.com/Bs5Yk4Yd
strace.zip

Another build error with latest master branch code instead of v1_beta19, failed at make menuconfig
•Soletta version (top commit hash): master (commit 6f93cf1042)
.cpnfig : NIL
config.log : http://pastebin.com/EMHFYZEh
make log : http://pastebin.com/ETXwvaTu
make strace log (strace -ff make &> strace.log): strace.zip
make strace log (strace -ff make menuconfig &> strace.log): strace2.zip
strace.zip
strace2.zip

This happens  when you forget to unset pkg_config_path ? This is usually
the case with this error.
On Tue, May 10, 2016, 03:31 LB Lim<EMAIL_ADDRESS>wrote:

Another build error with latest master branch code instead of v1_beta19,
failed at make menuconfig
•Soletta version (top commit hash): master (commit 6f93cf1
https://github.com/solettaproject/soletta/commit/6f93cf1042e4b7ec04208821f5622b566b04f407
)
.cpnfig : NIL
config.log : http://pastebin.com/EMHFYZEh
make log : http://pastebin.com/ETXwvaTu
make strace log (strace -ff make &> strace.log): strace.zip
make strace log (strace -ff make menuconfig &> strace.log): strace2.zip
strace.zip
https://github.com/solettaproject/soletta/files/256490/strace.zip
strace2.zip
https://github.com/solettaproject/soletta/files/256491/strace2.zip
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/solettaproject/soletta/issues/1941#issuecomment-218070398

Nope, I have unset the PKG_CONFIG_PATH. This is the script I used to build and reproduce the prb
cd mywork/soletta
git pull
make distclean
git clean -dfx
git submodule init && git submodule update
source /opt/quark_sdk/1.7.2/environment-setup-i586-poky-linux
unset PYTHONHOME
export TARGETCC=$CC
export TARGETAR=$AR
unset PKG_CONFIG_PATH
make menuconfig

likely @mbelluzzo wrote one thing to mean the other: If you set PKG_CONFIG_PATH and PKG_CONFIG_LIBDIR you can avoid the cross compilation to look at your host.
That is, if you unset (as he wrote), then you're likely using /usr/lib/pkgconfig while you'd be interested in /opt/quark_sdk/1.7.2/usr/lib/pkgconfig (or something like that), that would include dependencies for libcurl, icu, mosquitto, microhttpd and so on.

Also, looking at your pastebins. I'd recommend to rebase to last master as we're improving some bits, I se converter/string-format.c but that's now at format/string-format.c, the warning looks harmless there.
The warning in sol-memmap-storage.c:178 is also strange, fread(&old_value, entry->size, 1, file); with old_value being uint64_t (8 bytes), then entry->size is checked to be less or equal 8 with an assert: assert(entry->size <= 8);, so the supposed error from the compiler can never be reached.
The actual build error is resulting from an internal compiler error, that is, GCC itself is crashing.
My recommendation is to skip the old GCC and try a newer toolchain with 5.3, like the one in Ostro.

Nope, I meant unset. We unset PKG_CONFIG_PATH so our host tools find the needed dependencies just fine (IOW do not look on the sdk to compile host stuff), like ncurses to display the menuconfig. And this doesn't break the cross compile because it's done through --sysroot flags everywhere and therefore should use the dir pointed at PKG_CONFIG_SYSROOT_DIR for everything related to it (iow the target dependencies), avoiding the mix of host and target dependencies. Unless something changed on yocto 1.7.2 environment script.

then you're lucky, because it makes no sense :-D PKG_CONFIG_SYSROOT_DIR affects ${prefix} replacement.
Or pkg-config that is being used is the one provided by the SDK, usually patched to assume PKG_CONFIG_LIBDIR to the sdk installation path

make V=1 while I cross compile says I'm not having luck, just pointing
things to the right stuff.
On Wed, May 11, 2016 at 2:48 PM, Gustavo Sverzut Barbieri <
<EMAIL_ADDRESS>wrote:

then you're lucky, because it makes no sense :-D PKG_CONFIG_SYSROOT_DIR
affects ${prefix} replacement.
Or pkg-config that is being used is the one provided by the SDK, usually
patched to assume PKG_CONFIG_LIBDIR to the sdk installation path
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/solettaproject/soletta/issues/1941#issuecomment-218536447

nice way to try this is to install a -dev package on your host that you do not have on your target, like icu-dev or something like this. See if make reconf is detecting it on your host and not on cross-compile.

That is already the case when I compile Soletta to run on original Edison
(with the original SDK), and works just fine, including an observation that
"You're building the string nodes module without i18n support.", because
the dependency isn't on the target, but it is on my host.
On Wed, May 11, 2016 at 3:40 PM, Gustavo Sverzut Barbieri <
<EMAIL_ADDRESS>wrote:

nice way to try this is to install a -dev package on your host that you
do not have on your target, like icu-dev or something like this. See if make
reconf is detecting it on your host and not on cross-compile.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/solettaproject/soletta/issues/1941#issuecomment-218551200


:children_crossing: Optimize Boolean verification

Optimize can not verify boolean "true" and "false".

I think this is not good.
Sorry, my English is poor.
These are the screenshots I'm using.

This is a breaking :boom: change. Better to target it to master.

@Dylan-DPC Thanks, I will resubmit pull request.

@frowhy you should use 0 or 1 in the url.


ETH/USD (ETH/USD) is at 1,827.40 (-3.13%)

ETH/USD (ETH/USD) is at 1,827.40 (-3.13%)
http://www.investing.com/crypto/ethereum/eth-usd?utm_source=investing_app&utm_medium=share_link&utm_campaign=share_instrument

,u@my

Please don't post irrelevant issues like this.


Rename Elastic.CommonSchema.Serilog.Sink => Elastic.Serilog.Sinks

The readme still references the old name.


wasm-opt flags -Os vs. -Oz

Locally I'm testing the two optimization modes with wasm-opt version 110:
$ wasm-opt --help
  …
   -Os                                          execute default optimization
                                                passes, focusing on code size

   -Oz                                          execute default optimization
                                                passes, super-focusing on code
                                                size
  …

For my tests, there is a difference in the order of magnitute of 1-2%:
# -Os

-rwxr-xr-x  1 me  staff  192130 16 Okt 17:27 nois_demo.wasm
-rwxr-xr-x  1 me  staff  480903 16 Okt 17:27 nois_oracle.wasm
-rwxr-xr-x  1 me  staff  225705 16 Okt 17:27 nois_proxy.wasm

# -Oz

-rwxr-xr-x  1 me  staff  189263 16 Okt 17:29 nois_demo.wasm
-rwxr-xr-x  1 me  staff  472586 16 Okt 17:29 nois_oracle.wasm
-rwxr-xr-x  1 me  staff  223632 16 Okt 17:29 nois_proxy.wasm

So for now I don't see a strong need to move away from the well established -Os.

Some more example numbers: https://twitter.com/const_amit/status/1752210883156062660/photo/1


Servlet version error catching

What does this PR do?
Catches and orderly logs error trying to obtain Servlet API version. This only affects agent logging for debugging purposes. Hopefully, if fails for one Servlet or only on init, it can still work with another Servlet or through the service instrumentation.
Checklist

[x] This is a bugfix

[ ] I have updated CHANGELOG.asciidoc
[ ] I have added tests that would fail without this fix
[ ] The reporting user confirmed the fix

Since this version-discovery instrumentation allocates an Object[] and since it is applied to Servlet#service(), which is heavily invoked, I also added a check that utilizes the co.elastic.apm.agent.util.LoggerUtils.LogOnceLogger capability to disable logging after the first usage.

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

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

Expand to view the summary

Build stats

Start Time: 2022-05-10T07:23:03.348+0000

Duration: 35 min 39 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
2259

Skipped
14

Total
2273

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

/test : Re-trigger the build.

run benchmark tests : Run the benchmark tests.

run jdk compatibility tests : Run the JDK Compatibility tests.

run integration tests : Run the Agent Integration tests.

run end-to-end tests : Run the APM-ITs.

run windows tests : Build & tests on windows.

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


Initial ORCJIT Bindings

This patch provides an initial set of ORCJIT bindings. They're incomplete, and the ORC API will evolve past this in the near future.

From a cursory glance, this is missing

[ ] LLVMOrcGetMangledSymbol
[ ] LLVMOrcDisposeMangledSymbol
[ ] LLVMOrcCreateIndirectStub
[ ] LLVMOrcSetIndirectStubPointer

Subsumed by #158


Enhance Pynecone with Custom React Hooks

Hi team, I am trying to compile a mui data table js script.
My custom mui data table script is
`
  class CustomTag(pc.Component):

      library = '@mui/material/styles'

      tag = 'ThemeProvider'

      # style: pc.Var[Dict]

      def _get_imports(self):
          return pc.utils.merge_imports(
              super()._get_imports(), {"@mui/material/styles": {"createTheme"}, })

      def _get_custom_code(self) -> Optional[str]:
          return """ const theme = createTheme({
                  components: {
                      MUIDataTableBodyCell: {
                          styleOverrides:{
                              root: {
                                  backgroundColor: "#FFFFFF"
                              }
                          }
                      }
                  }
               })
          """

      def get_custom_code(self) -> Set[str]:
          # Store the code in a set to avoid duplicates.
          code = set()

          # Add the custom code for this component.
          custom_code = self._get_custom_code()
          if custom_code is not None:
              code.add(custom_code)

          return code

      @classmethod
      def create(
              cls, *children, data=None, columns=None, options=None, **props
      ) -> pc.Component:
          """Create a custom tag component.
          """
          if len(children) == 0:
              children = []
              if data:
                  children.append(MUIDataTables.create(data=data, columns=columns, options=options))

          return super().create(*children, **props)

  class MUIDataTables(pc.Component):
      """A component that wraps ag grid component."""

      library = "mui-datatables"

      tag = "MUIDataTable"

      data: pc.Var[List[List]]

      columns: pc.Var[List]

      options: pc.Var[Dict]

      # def render(self):
      #     Imports = self.get_imports()

  mui_dt = CustomTag.create

  columns = ["Name", "Title", "Location"]

  data = [["Gabby George", "Business Analyst", "Minneapolis"],
      [
        "Aiden Lloyd",
        "Business Consultant for an International Company and CEO of Tony's Burger Palace",
        "Dallas"
      ],
      ["Jaden Collins", "Attorney", "Santa Ana"],
      ["Franky Rees", "Business Analyst", "St. Petersburg"],
      ["Aaren Rose", None, "Toledo"],
      ["Johnny Jones", "Business Analyst", "St. Petersburg"],
      ["Jimmy Johns", "Business Analyst", "Baltimore"],
      ["Jack Jackson", "Business Analyst", "El Paso"],
      ["Joe Jones", "Computer Programmer", "El Paso"],
      ["Jacky Jackson", "Business Consultant", "Baltimore"],
      ["Jo Jo", "Software Developer", "Washington DC"],
      ["Donna Marie", "Business Manager", "Annapolis"]]

  options = {'filter': True, 'filterType': 'dropdown', 'responsive': 'vertical',
                             'tableBodyHeight': '600px'}

  # style = {'components': {'MUIDataTableBodyCell': {'styleOverrides': {'root': {'backgroundColor': "#FFFFFF"}}}}}

  class State(pc.State):
      """The app state."""
      pass

  def index():
      return pc.center(pc.box(mui_dt(columns=columns, data=data,
                              options=options)),
                       width='1900px',
                       height='900px')

  # Add state and page to the app.

  app = pc.App(state=State)
  app.add_page(index)
  app.compile()

`
My compiled js code that I want is
`
  import {useEffect, useRef, useState} from "react"

  import {useRouter} from "next/router"

  import {E, connect, updateState} from "/utils/state"

  import "focus-visible/dist/focus-visible"

  import {Box, Center, useColorMode} from "@chakra-ui/react"

  import {ThemeProvider, createTheme} from "@mui/material/styles"

  import MUIDataTable from "mui-datatables"

  import NextHead from "next/head"

   const theme = createTheme({
                  components: {
                      MUIDataTableBodyCell: {
                          styleOverrides:{
                              root: {
                                  backgroundColor: "#FFFFFF"
                              }
                          }
                      }
                  }
               })

  const EVENT = "ws://localhost:8000/event"

  export default function Component() {

  const [state, setState] = useState({"events": [{"name": "state.hydrate"}]})

  const [result, setResult] = useState({"state": null, "events": [], "processing": false})

  const router = useRouter()

  const socket = useRef(null)

  const { isReady } = router;

  const { colorMode, toggleColorMode } = useColorMode()

  const Event = events => setState({

    ...state,

    events: [...state.events, ...events],

  })

  useEffect(() => {

    if(!isReady) {

      return;

    }

    const reconnectSocket = () => {

      socket.current.reconnect()

    }

    if (typeof socket.current !== 'undefined') {

      if (!socket.current) {

        window.addEventListener('focus', reconnectSocket)

        connect(socket, state, setState, result, setResult, router, EVENT)

      }

    }

    const update = async () => {

      if (result.state != null) {

        setState({

          ...result.state,

          events: [...state.events, ...result.events],

        })

        setResult({

          state: null,

          events: [],

          processing: false,

        })

      }

      await updateState(state, setState, result, setResult, router, socket.current)

    }

    update()

  })

  return (

  <Box><ThemeProvider theme={theme}><MUIDataTable columns={["Name", "Title", "Location"]}

  options={{"filter": true, "filterType": "dropdown", "responsive": "vertical", "tableBodyHeight": "600px"}}

  data={[["Gabby George", "Business Analyst", "Minneapolis"], ["Aiden Lloyd", "Business Consultant for an International Company and CEO of Tony's Burger Palace", "Dallas"], ["Jaden Collins", "Attorney", "Santa Ana"], ["Franky Rees", "Business Analyst", "St. Petersburg"], ["Aaren Rose", null, "Toledo"], ["Johnny Jones", "Business Analyst", "St. Petersburg"], ["Jimmy Johns", "Business Analyst", "Baltimore"], ["Jack Jackson", "Business Analyst", "El Paso"], ["Joe Jones", "Computer Programmer", "El Paso"], ["Jacky Jackson", "Business Consultant", "Baltimore"], ["Jo Jo", "Software Developer", "Washington DC"], ["Donna Marie", "Business Manager", "Annapolis"]]}/></ThemeProvider></Box>

  <NextHead><title>{`Pynecone App`}</title>

  <meta name="description"

  content="A Pynecone app."/>

  <meta content="favicon.ico"

  property="og:image"/></NextHead>

  )

  }

`
The problem to get this table working in pynecone is that there is no way to add the create theme hook in the component. Am I missing something here? Need some help on this. If not, do we have adding custom hooks in the roadmap. This will exponentially increase pynecone's extendibility and community driven add-ons and plugins.

This might be duplicate to #55.

Yeah it's a duplicate, but I think we will have time to add this feature soon. We have been focusing on fixing the core but will now have more time to start implementing features like this. Thanks for bringing this up

This was added in #810


Merge CosmosAsyncResponse and CosmosResponse

Merge CosmosAsync*Response and Cosmos*Response and just have one single type - which is CosmosResponse
Remove parent proxy types from response object.

This is done.


Codigo agosto23

Merge 2023.2 code with previous semesters

Merged with new code prepared for semester 2023.


German translation

@k1ngf15h3r and @sebki
Please review and correct mistakes if any :smile:

Looks good :)

could  one  merge this?


Error handling

Currently emitting invalid state transition emits error nanostate.emit: invalid transition ${this.state} -> ${eventName}.
Do you have any ideas on how to handle those errors? E.g.
var machine = nanostate('cash', {
  cash: { check: 'check' },
  check: { cash: 'cash' }
})

machine.onError((e) => {
  console.log(error)
  throw e
})

machine.emit('robbery')

I wouldn't.
Better make sure the string passed to machine.emit() is a registered event in the first place.
Here's a line from the choo readme that summarizes why:

We use the require('assert') module from Node core to provide helpful error messages in development. In production you probably want to strip this using unassertify.

Do you feel like there would be a good case for managing invalid transitions internally?
I could imagine two ways this could work. Maybe:

we could emit an event. a nanostate instance is already an event emitter which means  .on is already exposed; the pattern should probably be: machine.on('error', ...)
we could return a list of all possible states so that consumer can run the check in the application code. this comes at the cost of being tiny. maybe it's worth it? i don't know ¯\(ツ)/¯

For now I try to make sure I emit only registered event names.
I hope this helps :)

@vorg hey, yeah - so the idea behind throwing an error here is that you've made a mistake in the logic. In any given scenario, if you hit an invalid transition, there's no good way to recover from that. Which state did you intend to go? Which state should we be in to recover? There's no good answer.
So we throw.
As per https://github.com/choojs/nanocomponent/issues/43, hopefully for use within nanocomponent, we'll have error boundaries in the (near) future. These are basically try..catch blocks around all internal methods, calling an optional error handler if something goes wrong.
Does this make sense?

I'm going to prioritize that next, should be a fairly easy addition.

Hi,
Yes it makes sense. For now i can also validate potential changes by
accessing machine.transitions which is enough for me.
On Mon, 12 Feb 2018 at 16:44, Bret Comnes<EMAIL_ADDRESS>wrote:

I'm going to prioritize that next, should be a fairly easy addition.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/choojs/nanostate/issues/10#issuecomment-364983547,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKb-Q7oRFQD-jbM4-sWDr71Exnh6lywks5tUGqJgaJpZM4SASW8
.

--
Marcin Ignac


Candlestick upColor and downColor is not changed on applyOptions

Lightweight Charts Version: 3.3.0
Steps/code to reproduce:
import { BarData, createChart } from "lightweight-charts";

const chartRoot = document.getElementById("main-chart") as HTMLDivElement;
const chart = createChart(chartRoot, {
  width: 800,
  height: 600
});

const candlestick = chart.addCandlestickSeries({
  upColor: "rgb(0,255,0)",
  downColor: "rgb(255,0,0)"
});

const data: BarData[] = [
  {
    time: "2021-06-04",
    open: 1000,
    high: 1200,
    low: 800,
    close: 900
  },
  {
    time: "2021-06-05",
    open: 1000,
    high: 1200,
    low: 800,
    close: 1100
  }
];

candlestick.setData(data);

setTimeout(() => {
  candlestick.applyOptions({
    upColor: "rgb(0,0,255)",
    downColor: "rgb(0,255,0)"
  });
}, 2000);

setTimeout(() => {
  candlestick.applyOptions({
    upColor: "rgb(0,255,255)",
    downColor: "rgb(255,255,0)"
  });
}, 4000);

Actual behavior:
Candlestick color doesn't change at all
Expected behavior:
Candlestick color should change after applyOptions
Screenshots:

After last applyOptions, candlestick color still not changed, it should be yellow down and light blue up
CodeSandbox/JSFiddle/etc link:

Here a jsfiddle to reproduce the issue
This does not seem to be a recent issue at all / regression. I get the same behavior on 1.x versions of Lightweight Charts

It seems this function called on setData but not applyOptions, hence the _items PaneView still use old style
https://github.com/tradingview/lightweight-charts/blob/cb973d2b460aa187b0b8b5bc8bc327ee072796e5/src/model/series-bar-colorer.ts#L82-L101

Looks like a bug. Probably we don't update colors when the only options are applied


Update Magnum and m.css to latest

Motivation and Context
Note: Requires https://github.com/facebookresearch/habitat-lab/pull/1776 in order to pass the CI. The lab PR can be merged independently, as the syntax should work even with the original code.
Another ~2 months worth of Magnum features, fixes and improvements. What's new since #2278:

Fixed compatibility with Emscripten 3.1.49+
Fixed Matrix::isOrthogonal() to catch negative dot product values. Note that this effectively tightens up certain assertions and could cause previously-incorrect but seemingly working code to assert (or raise an exception in Python). Thanks to @jturner65 for the discovery.
New Math::join() overload that joins a range and a point, in addition to joining two ranges. Requested by @jturner65.
Low-level refactoring in the Math library, resulting in better runtime perf in debug builds and most Vector operators being now constexpr
New Quaternion::rotation() overload for creating a rotation from one vector to another. Matches Eigen's Quaternion::setFromTwoVectors() and similar APIs in other quaternion libraries. Related to #2301, it felt better to just put this in Magnum instead of having to maintain a utility function in Habitat.
Made the GlslangShaderConverter plugin work with glslang 14.0. Not directly used in Habitat, but affects various packages where it is enabled by default, such as Homebrew, where a build failure was hit by @eundersander.
New MAGNUM_BUILD_PYTHON_BINDINGS_RTLD_GLOBAL CMake option for Python bindings. Enabled by default for static builds, performs sys.setdlopenflags(sys.getdlopenflags()|ctypes.RTLD_GLOBAL) before loading native modules in an attempt to resolve cursed issues with deduplicating globals across shared modules that was made impossible by Python implicitly isolating each loaded module into its namespace, which was repeatedly hit by @eundersander, @0mdc and others. I'm writing very long sentences today, yes, sorry.
Exposed trade.MeshAttributeData and trade.SceneFieldData classes to Python, which together with meshtools.interleave() and scenetools.combine_fields() finally allows trade.MeshData and trade.SceneData to be created from scratch in pure Python. Which in turn opens possibilities for adding new attributes to existing meshes, such as annotating skinned meshes with bone influences. Or for building whole scene hierarchies from loose meshes, materials and such, and exporting those to glTF. This was also the last main blocker that prevented writing the batch renderer composite file generation pipeline (#1969) in pure Python.

Also updated the m.css submodule, because apparently it was untouched since December 2022(!):

Fixed compatibility with newer docutils
Fixed compatibility with dvisvgm < 3.0 and Ghostscript 10
Improved highlighting of ANSI-colored terminal output
Ability to style <video> tags the same as images
Detecting new builtins in Python 3.11 and omitting them from output if they're not overriden and documented by the user
No longer using deprecated distutils, thus fixing compatibility with Python 3.12
Recognizing / and * in pybind11 signatures (which is used heavily by new Magnum bindings, such as SceneFieldData constructors)

How Has This Been Tested
:green_circle:

Re-running the failed lab build with the lab PR merged: https://app.circleci.com/pipelines/github/facebookresearch/habitat-sim/12613/workflows/de0d49c1-7011-42bb-ac1e-18f98ff912c6/jobs/79832
I have to leave for today, feel free to merge once this build passes. (Not sure if the re-ran build shows up in the overview above, I hope it will?)


Starter Auth Helpers with Nextjs App Router doesn't work

Bug report

[X ] I confirm this is a bug with Supabase, not with my own application.
[X ] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
Starter App using nextjs app router doesnt work.
To Reproduce

Go to 'https://supabase.com/docs/guides/auth/auth-helpers/nextjs?language=ts'
Follow instructions under Automatic Configuration
Run yarn dev (with correct environment variables)
Attempt sign up with new user (email) and password
Page reloads with message "could not authenticate user" no browser console errors, no terminal errors

Expected behavior
1 - supabase user is created in auth schema
2 - user creation is confirmed.
Screenshots

System information
@supabase/auth-helpers-nextjs": "^0.8.1",
@supabase/supabase-js": "^2.38.1",
node 20.8.0
Add any other context about the problem here.

Can't replicate, please provide a reproducible example repo with the issue you are having. Also note we've updated the Next.js template in recent times so please try it out again.

hey @silentworks closing this as it was answered / resolved in the main supabase repo i created - TLDR for anyone running into this, wrong SMTP config results in this (generic) error on the frontend.


Support for custom elements

Describe Problem
currently only basic elements work. We should provide a migration for custom elements and allow for users to define custom element query selectors.
Suggest Solution
Work would start here on the various selectors:
https://github.com/ParamagicDev/mrujs/blob/ca3820a7d6e62d1e34a77d62cfd3a764872c8fc4/src/utils/dom.ts#L29

selectors arent the solution. Let the web-component library handle it, perhaps mrujs can expose the functions, but dont go out of our way either.


Add extend function for grid_map

Additional features for extending the map. And there is a problem with the conversion from coordinates to grid, which has been fixed by adding const ERROR_CORRECTION.
If there is a better way, I would like to use it.

I also feel that the test results are not right.

Thanks for your clear explanation.
I think my test cases are not good. I should not test the edge cases because float values are not stable. It's OK to avoid the edge values, I think.


Fix HAL calls to check fast IO under device OS 5.x

Problem
This CAN library fails to compile under device OS 5.x because some of the HAL API names were changed.
Solution
Check the version of device OS being compiled against and use the appropriate HAL API.

@mfarver and @pkourany


Audio Player Only - Horizontal Volume

Audio Player only:
Firefox 18-22.. volume break and go to left side..
Problem: table-cell
Fix:
.mejs-controls a.mejs-horizontal-volume-slider  {display: table;}
just to check is it good in other IE,Safari etc..

@apsolut Closing old issues. If you'd like to reopen this, let us know. Thanks!


Document yaml anchors

@basnijholt, currently yaml anchors are working fine, do you intend to keep this behaviour? If so, i would like to add some examples or at least a notice.

I didn’t know that this would work. Yes please add some examples! Much appreciated 😄

I was quite happy to find it -> it does work pretty well. I will document this after some more thoughts went into #103. So people do not migrate everything to yaml anchroch and than again to templates.


Failed to detect running Functions host within "60" seconds. You may want to adjust

Repro steps:

Action: azureFunctions.pickProcess
Error type: Error
Error Message: Failed to detect running Functions host within "60" seconds. You may want to adjust the "azureFunctions.pickProcessTimeout" setting.
Version: 0.20.0
OS: win32
Product: Visual Studio Code
Product Version: 1.40.2
Language: en

Call Stack
extension.bundle.js:353:75291extension.bundle.js:353:75291
o extension.bundle.js:353:73918

Hi @SatishPaiB
Thanks for reporting.  Please provide repro steps.


Fix styling and spacing issues according to Figma file

Fix styling and spacing issues according to Figma file

There are 2 variants on the homepage i.e. Individual and Enterprise so make sure we analyze both and then start with fixing this UI issues.

https://www.figma.com/design/Q8AoW8o4i2RqeFCj4cf8HJ/FF-Homepage-2024?node-id=3074-22353&t=ntqOMTcwxlP6zVb0-0

I am going to close this issue as figma file isnt updated with latest design and create even more variance between the styling and spacing. Ill let @tom-hightower raise issues and fix them adhoc manner
Figma file can be used as piece of information but will not be matching things 1:1


Change Reset Workflow icon

What type of PR is this? (check all applicable)

[ ] Refactor
[ ] Feature
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update
[ ] Community Node Submission

Have you discussed this change with the InvokeAI team?

[ ] Yes
[ ] No, because:

Have you updated all relevant documentation?

[ ] Yes
[ ] No

Description
Just a Suggestion to change the reset workflow button style, to be more as a reset style icon, then a trash icon

Related Tickets & Documents

Related Issue #
Closes #

QA Instructions, Screenshots, Recordings

Added/updated tests?

[ ] Yes
[ ] No : please replace this line with details on why tests
have not been included

[optional] Are there any post deployment tasks we need to perform?

I don't think we should change the icon. We have a convention that "red trash can means destructive delete action".
I'd rather provide some feedback to the user via eg a modal. How does that sound?

Icons need to change. The UX pattern is not contextually similar, and multiple users have expressed confusion.

@psychedelicious -- UX Rationale:
Queue - Now has a "halt & burn the queue" icon. Not really a 'trash' icon function.
Workflow - Has a "clear work area" icon - I've copied this to canvas as that is also probably an inappropriate trash can.
Images - Trash can. Images go to the recycling bin.
Open to different icons, but these three are distinct enough to merit not sharing one.

+1 for changing it, the ControlNet UI already uses this icon in the same way for a reset functionality

I understand the need to clarify actions and icons' meanings.
In this PR, on canvas, the same icon is used for both undo and reset - that's confusing:

If we can clarify actions by using icons, great, but first let's look at all the destructive actions you can take in the app and the icons that go with them (possible I'm missing some):

Clear canvas -> destructive -> trashcan
Clear canvas mask -> destructive -> trashcan
Clear workflow -> destructive & (currently) irreversible action -> trashcan
Clear queue -> including canceling the current item, destructive & irreversible -> trashcan
Cancel current queue item -> destructive & irreversible -> x, because there's already a trashcan just next to it
Delete image -> destructive & (currently) irreversible -> trashcan
Delete board -> destructive & (currently) irreversible -> trashcan
Reset any set-able image (control adapters, init image) -> resets the image, which you can trivially drag back on to the image area, non-destructive -> undo icon
Delete controlnet itself -> destructive -> trashcan
Delete lora -> destructive -> trashcan
Delete linear UI field -> destructive -> trashcan
Discard staging area -> destructive -> x

If we are going to change the icon used for each action, we should consider all of these actions and choose appropriate representations for each. The icons shouldn't be changing regularly, let's take the time to choose the right symbols once. They are pretty consistent right now.
(The reset image icon should be changed to not be the undo icon. That's undo/redo everywhere and there shouldn't be anything else that uses the same icon. Probably that should be an x instead.)

(The reset image icon should be changed to not be the undo icon. That's undo/redo everywhere and there shouldn't be anything else that uses the same icon. Probably that should be an x instead.)

I forgot about the canvas undo redo, was just suggesting it as the clear node and controlnet image used it
maybe

Another limitation I often bump into is with FA5. Sometimes the set just doesn't have an icons we need. Eventually as we keep adding new stuff, think we will need to design our own icon packs and maintain them. But that's a future future problem.

Glancing over that list, I count 5 kinds of actions in 3 groups:
Reversible destructive

Destructive, reversible, single entity
Destructive, reversible, multiple entities

Irreversible destructive

Destructive, irreversible, single entity
Destructive, irreversible, multiple entities

Reset

Reset, single entity

That implies 3 or 5 icons, depending on if we want to split up single vs multiple entities.
Also, some actions are unique enough that maybe they should have their own icon, but until we pay somebody to an icon set for us, it may be hard to fine icons that feel cohesive for all these different things.

@mickr777 That icon has inherent meaning though - recycle, use this entity for something new.
Similarly, the undo icon means "go back one step". That's why it's used for the set-able images - you can only go back one step with that action. Though, as mentioned, I think these maybe should use the x or some other icon instead.

I'm less concerned about which icon we settle on and more concerned about the very clear need for improved UX here.
I've determined the main reason for confusion is that a common UX for deletion is to use the Delete Icon in the Toolbar to manage the deletion of images in the gallery. When viewing the gallery in the Workflow editor, the Trash Can is deceptively present, but functions completely differently.
Needs a different UX.

@Millu can you work through the list and put some thought to it so we can make sure this PR gets in?


Add ros2_easy_test

Please Add This Package to be indexed in the rosdistro.
rolling
The source is here:
https://github.com/felixdivo/ros2-easy-test
Checks

[x] All packages have a declared license in the package.xml
[x] This repository has a LICENSE file
[x] This package is expected to build on the submitted rosdistro

Notes
Replaces https://github.com/ros/rosdistro/pull/39892
@felixdivo you marked it help-wanted so I'd gave it a shot here.

@Timple There is now a version 0.3.0.

@Timple There is now a version 0.3.0.

Great, that's what we'll use for the binaries after this PR is approved/merged

I did not find any documentation on how to make new releases (e.g., via git tags, by package.xml, etc.; and if this is scraped automatically). Is this the right process?

Step one is getting this PR merged. That's kind of like the approval for the package and package name.

Holding for an upcoming Rolling sync.

[x] At least one of the following must be present

[x] Top level license file:
[ ] Per package license files:

[x] License is OSI-approved:  MIT
[x] License correctly listed in package.xmls
[x] Public source repo: https://github.com/felixdivo/ros2-easy-test
[x] Source repository contains ROS packages
[x] Each package meets REP-144 naming conventions

Package name details
$ find . -name "package.xml" -exec grep --color=auto -e "<name>" "{}" ";"
<name>ros2_easy_test</name>

License details
$ find . -name "package.xml" -exec grep --color=auto -e "<license>" "{}" "+"
<license>MIT</license>


spawnCreep changes

[ ] ConstructionCost should contain rampart
[ ] GameObject is now extended
[ ] move and moveTo can return undefined
[ ] SPAWN_ENERGY_CAPACITY & SPAWN_HITS
[ ] spawnCreep & createConstructionSite returns an object with the object or an error, there seems to be breakingchange support
[ ] construction cost should contain structurespawn

Add STRUCTURE_SPAWN to BuildableStructureConstant

Add STRUCTURE_SPAWN to BuildableStructureConstant
ConstructionSite should contains structure prototype

I can only see a structurePrototypeName not a structure


[FLINK-15839] [kafka-io] Fix Stateful Functions KafkaIngressBuilder properties resolution logic

This PR revisits how we resolve configs for the KafkaIngressBuilder, given that we have:

Named configuration methods for important settings
Some of which have default values, some don't
Some eventually resolve as a Kafka client property, some are not
At the same time, also accept a Properties which may also explicitly define values for the above.

The end result of the changes in this PR is as follows:

Configs passed via named methods should always overwrite the value set via passed in Properties
Any default values for named configuration methods should be defined in the builder
If no config was passed via its named method, then we use the default value (if any) to overwrite the properties IFF the user also did not provide a value for it there.

The individual commits and their messages / descriptions should be sufficient in explaining what was changed to achieve this.

New tests in KafkaIngressBuilderTest was added to verify the changes.
Please also see there to get an overview of the expected behaviour.

cc @igalshilman this is the follow-up to #5, concerning the config resolution issue.

Merging after Travis is green ...


ESC going to layer initian, even when I removed the key-combo from config file

Hi. I would like to make the escape key work as usual, while not exiting the mouse layer, but ESC is always going back to the initial layer whenever I press it.
This is my config file:
# the keyboard devices it reads from, if no devices are specified, it reads from all
devices:
  - "/dev/input/by-id/usb-LITEON_Technology_USB_Keyboard-event-kbd"
# - "/dev/input/by-id/SOME_KEYBOARD_REPLACE_ME-event-kbd"

# this is executed when mouseless starts, e.g. useful for setting the keyboard layout
# startCommand: "setxkbmap de"

# the default speed for mouse movement and scrolling
baseMouseSpeed: 750.0
baseScrollSpeed: 20.0

# the time it takes to accelerate to baseMouseSpeed (in ms), 0 to reach top speed immediately
mouseAccelerationTime: 200.0
# the shape of the acceleration curve, 1.0 is linear, higher values have more time at low speeds
mouseAccelerationCurve: 2.0
# speed of the mouse when it starts moving
startMouseSpeed: 0.0
# same for deceleration
mouseDecelerationTime: 300.0
mouseDecelerationCurve: 3.0

# the rest of the config defines the layers with their bindings
layers:
# the first layer is active at start
- name: initial
  bindings:
    # when tab is held and another key pressed, activate mouse layer
    # tab: tap-hold-next tab ; toggle-layer mouse ; 500
    numlock: tap-hold-next numlock ; toggle-layer mouse ; 500
    # when a is held for 300ms, activate mouse layer
    #a: tap-hold a ; toggle-layer mouse ; 300
    ## right alt key toggles arrows layer
    # rightalt: toggle-layer arrows
    ## switch escape with capslock
    # esc: capslock
    # capslock: esc
# a layer for mouse movement
- name: mouse
  # when true, keys that are not mapped keep their original meaning
  passThrough: true
  bindings:
    # quit mouse layer
    # q: layer initial

    z: layer initial
    # keep the mouse layer active
    space: layer mouse
    r: reload-config
    # l: move  1  0
    # j: move -1  0
    # k: move  0  1
    # i: move  0 -1
    d: move  1  0
    a: move -1  0
    s: move  0  1
    w: move  0 -1
    # p: scroll up
    # n: scroll down
    leftbrace: scroll up
    apostrophe: scroll down
    rightshift: speed 4.0
    # leftalt: speed 4.0
    # e: speed 0.3
    # w: speed 0.1
    rightctrl: speed 0.3
    compose: speed 0.1
    # capslock: speed 0.1
    # f: button left
    # d: button middle
    # s: button right
    semicolon: button left
    p: button middle
    rightbrace: button right
    # move to the top left corner
    k0: "exec xdotool mousemove 0 0"
# # another layer for arrows and some other keys
# - name: arrows
#   passThrough: false
#   bindings:
#     e: up
#     s: left
#     d: down
#     f: right
#     q: esc
#     w: backspace
#     r: delete
#     v: enter
#     # _ is the wildcard key, which matches any key that is not mapped
#     _: rightalt+_

Yes you're right, I did this so that one can always go to the initial layer and not get stuck somewhere else, but would be good if one could disable this.
I think what I will do is disable this when one explicitly maps the esc key, so in your case one could add a binding esc: esc to the mouse layer.

It's really nice that you thought about avoiding the user getting stuck. Makes a lot of sense.
The option to explicitly disable the ESC default behavior or to disable when the key was mapped is perfect in my opinion.

i would highly appreciate this too to solve the inconsistency i have between mouseless and karabiner as i have space when held as a meta key and when i do hold space (navigation layer) + escape i get tmuxes copy vi modemm

This is now implemented, pressing esc does not go to the initial layer when it is mapped to something else.


{bp-15163} use atomic to protect f_refs

Summary
use atomic to protect f_refs
fix regresion from https://github.com/apache/nuttx/pull/14801
includes
https://github.com/apache/nuttx/pull/15202
Impact
RELEASE
Testing
CI

[Experimental Bot, please feedback here]
No, this PR description does not fully meet the NuttX requirements. While it provides some information, it lacks crucial details.  Here's a breakdown:
Missing/Insufficient Information:

Summary:

While it mentions using atomic operations and fixing a regression, it doesn't explain what f_refs is, why it needs atomic protection, and how the atomic operations achieve this protection.  What was the specific issue caused by the regression?
It mentions including another PR (#15202).  This should be clarified – is this PR dependent on #15202?  Does it supersede #15202?  Simply stating "includes" is ambiguous.

Impact:

"RELEASE" is not descriptive enough.  Does this mean it affects a release branch?  Which one?  The Impact section requires "YES/NO" answers for each category followed by descriptions if "YES." At minimum, it needs to explicitly address each of the impact categories (user, build, hardware, documentation, security, compatibility).  Even if the answer is NO, it should state "NO."

Testing:

"CI" is also insufficient.  While Continuous Integration testing is valuable, the requirements specifically ask for details about local testing.  What host and target platforms were tested? What specific tests were run?  The provided log sections are empty.  Real testing logs are needed to demonstrate the fix and that it doesn't introduce new issues.

How to Improve:

Elaborate on the Summary: Explain what f_refs represents and its function. Describe the specific issue the regression introduced (e.g., race conditions, crashes, data corruption). Explain how using atomic operations resolves the problem.  Clarify the relationship with PR #15202.

Complete the Impact Assessment:  Address all impact categories with "YES/NO" and provide explanations for any "YES" responses.  If there is no impact in a category, explicitly state "NO."  For "RELEASE," specify which release is affected.

Provide Detailed Testing Information: List the specific build host(s) and target(s) used for testing, including OS, CPU architecture, compiler, and board/configuration details.  Include actual testing logs (or relevant snippets) demonstrating the problem before the change and the correct behavior after the change.  Even if CI tests pass, demonstrating local testing is essential for review.

By providing this missing information, the PR will meet the NuttX requirements and be easier for reviewers to understand and evaluate.


Add sync-docs action

See: sourcefuse/arc-docs#26

:tada: This issue has been resolved in version 5.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: