Decoder seems to not include last block?

I'm working on moving my project from implode-decoder to your node-pkware.
I have previously gotten a decoder working with implode-decoder and so wanted to start with getting a side-by-side comparison of your decoders, before moving onto using the encoder as we've talking about in #3.
In the process, I think I've found a bug with your decoder.
Checkout my project. Quick setup:
git clone --branch wip-node-pkware https://github.com/cinderblock/EWD.git
cd EWD
mkdir -p samples
wget -cq --directory-prefix samples https://github.com/cinderblock/3-Phase-Driver/raw/master/Driver.{ewprj,ms14} &
npx npm@7 install
npm run dev -- --verbose samples/*

You will see the last 100 characters of output that were common to both. However, the output of your decoder is 7072 bytes shorter than expected, which the reference decoder gets correctly.
PS, I wrote some TypeScript types for you. Feel free to include them in your sources. I'd be happy to make a separate PR for those if you like.

Well, I think I found the intended API. There is a decoder._state.onInputFinished that wants to be called with its own callback to get the last bit of data. I've updated the branch to reflect this. However this API feels wrong, like I'm doing something silly, because I'm accessing what I assume is private _state. Yet it seems to decode correctly...
Looking into the code, this looks like it might be the intended design. I see a this._flush = state.onInputFinished in explode.js.
I'm curious, why are you using this API? It seems to me that a "stream" format would be more appropriate. What do you think?

Hi! _state is indeed private, but I need it to be accessible from the outside so that I can run my unit tests. onInputFinished should be called by the readstream as soon as it runs out of data.
Regarding streams explode and implode returns only a handler function, which can be given to a transform stream, but the algorithms need to know when the input data finishes, so I rely on injecting a callback function to the transform stream's _flush callback: https://nodejs.org/api/stream.html#stream_transform_flush_callback. It should be hooked up automatically as soon as the first bits of data: https://github.com/meszaros-lajos-gyorgy/node-pkware/blob/master/src/explode.js#L330
The above mentioned this._flush = ... part is a bit tricky, because this doesn't refer to the context of explode or implode, but to the transform stream that the callback will be added to.
The reason I go with explode and implode only returning a handler function and not a fully initialized transport stream is that I want to apply higher order functions to it before adding it to a pipeline. For example Arx Fatalis' files have a non-compressed and compressed part, which I need to split before utilizing explode or implode.

I've checked your code and you are calling the handler given by explode() directly, which should be haded over to a transport stream. I already have a small example in the readme on how to decompress buffers in the style of streams: https://github.com/meszaros-lajos-gyorgy/node-pkware#decompressing-buffer-with-no-offset-into-a-buffer
const { Readable } = require('stream')
const { explode, stream } = require('node-pkware')
const { through, streamToBuffer } = stream

Readable.from(buffer) // buffer is of type Buffer with compressed data
  .pipe(through(explode()))
  .pipe(
    streamToBuffer(decompressedData => {
      // decompressedData holds the decompressed buffer
    })
  )

Ah, I see. I failed to look at the docs thoroughly. Thank you.
Why did you choose to use this alternate stream library over Node.js's Stream library?

Please check, if you can make your code work with the example I provided and if so, then I'll close the ticket. I might create a simple function version of pkware explode once I'm done with the remaning things for implode.

Sure. Any thoughts on incorporating TypeScript types in what you publish? I'm happy to make a PR just for those.

I'm not a fan of typescript, but I don't deny that it would be a useful addition to many javascript developers. If you can add typescript support to the codebase, then I would be very greatful and as always, PRs are welcome!


Continuous connection question

This is a question, not a real issue.
What are the rules regarding  ConnectToKnownDeviceAsync ?
When does it fail / time out?
How do I use the cancellation token to indicate to stop this operation?
I basically want to have a thread that continuously searches for a known device and tries to maintain connectivity with it. What's the best way to achieve this?
(i.e., try to connect, if fail after some predefined amount of time, try again).

i do it in while(true) cicle, checking current connection state and connect if necessary

If your device is advertising when it accepts connection, I would check for the advertisement before starting the connection. This way you do not try if the device is not available.

@mullerch Are you saying that ble device can be connected without advertising?

@lamest No I don't. Usually device do advertise when they are connectable and I think it's a good thing. I don't know the specification about that.

ok, spec is that advertising is necessary to connection. So connection without discovery is same as with discovery but faster. Or this is how it appear to me

Take a look at #145 maybe there's something that can help you there


Fix/ gameOver.spec - Removes dialog element from  element to remain displayed when…

… menu closes. Adjusts gameOver.spec test to confirm overlay does not exist #272

Please check the following

[ ] Do the tests still pass? (see Run the Tests)
[ ] Is the code formatted properly? (see Linting (Formatting))
For New Features:

[ ] Have tests been added to cover any new features or fixes?
[ ] Has the documentation been updated accordingly?

Please describe additional details for testing this change

Resolves #272


Merge pull request #1 from apache/3.1

3.1
What is the purpose of the change
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #11673 (eaead39) into 3.1 (f8f89f2) will increase coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                3.1   #11673      +/-   ##
============================================
+ Coverage     64.69%   64.72%   +0.02%
  Complexity       14       14
============================================
  Files          1430     1430
  Lines         60020    60020
  Branches       8823     8823
============================================
+ Hits          38832    38849      +17
+ Misses        17111    17096      -15
+ Partials       4077     4075       -2

Impacted Files
Coverage Δ

...pache/dubbo/remoting/transport/AbstractServer.java
58.44% <0.00%> (-3.90%)
:arrow_down:

...bo/remoting/zookeeper/AbstractZookeeperClient.java
81.60% <0.00%> (-3.45%)
:arrow_down:

.../src/main/java/org/apache/dubbo/rpc/RpcStatus.java
80.95% <0.00%> (-1.20%)
:arrow_down:

...rg/apache/dubbo/common/timer/HashedWheelTimer.java
85.22% <0.00%> (-0.35%)
:arrow_down:

...he/dubbo/registry/zookeeper/ZookeeperRegistry.java
61.57% <0.00%> (ø)

.../dubbo/registry/integration/RegistryDirectory.java
45.58% <0.00%> (+0.35%)
:arrow_up:

.../dubbo/remoting/transport/netty4/NettyChannel.java
72.64% <0.00%> (+0.94%)
:arrow_up:

...apache/dubbo/rpc/protocol/dubbo/DubboProtocol.java
65.03% <0.00%> (+3.14%)
:arrow_up:

...ache/dubbo/common/extension/ExtensionDirector.java
96.66% <0.00%> (+3.33%)
:arrow_up:

...he/dubbo/remoting/transport/netty/NettyServer.java
73.68% <0.00%> (+3.50%)
:arrow_up:

... and 2 more

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


Swift 2.3

Hi, @basvankuijck please rebase to master.
Thanks.

Supported swift 2.3 in https://github.com/KyoheiG3/DynamicBlurView/pull/18.
Thank you.


Created a Fidelity Bond but "Start Earning" returns "Maker could not start, no confirmed coins."

I Created a Fidelity Bond but the button at the bottom "start earning" returns "Maker could not start, no confirmed coins." at the top of the Earn page.
If there is a problem - a way to fix it or at least some infos around the problem would be better here.
Actual behavior
Steps to reproduce the problem

Send bitcoin to wallet
Use Earn - Created a Fidelity Bond
Press "start earning"

Specifications

Version: raspiblitz 1.9.0
Platform: raspberry pi
Browser: firefox

Additional context
Error-Message on page (after pressing button "start earning) "Maker could not start, no confirmed coins." does not give any information on how to fix. There are def confirmed coins in my wallet and the coins are even confirmed in a Fidelity Bond as shown on same page.
Trying to get more infos (e.g. looking into the order book if my fidelity bond is active/existing there) returned nothing (could not find anything related to my bond in the order book...)
Is it a bug? Not really I guess but it is just confusing to present "Maker could not start, no confirmed coins." while my fidelity bond is active and shown on same page.
After creating the fidelity bond... do I have to press "start earning" or is this button only for users without fidelity bond?

There are def confirmed coins in my wallet and the coins are even confirmed in a Fidelity Bond as shown on same page.

Do you have other coins other than the bond?
Fidelity bonds are timelocked on the Bitcoin blockchain, and cannot be spent in any way until the timelock expires. You need some other coins, other then the fidelity bond.
See the documentation:

https://jamdocs.org/interface/fidelity-bonds/
https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/master/docs/fidelity-bonds.md

It is impossible to move or spend funds that are locked in a fidelity bond before the bond expires. They cannot be used in collaborative transactions as fidelity bonds are time-locked by the Bitcoin protocol.

Thank you PC, I did in fact just understand that wrong.

This is indeed a UX problem that must be addressed. Thanks for reporting.

https://www.figma.com/file/kfejZJFlwBywvLEnPEmJo1/JoinMarket-UI?node-id=5604%3A67014&t=sIEGlehebAvdIjb1-11
we poured already some thoughts into this problem, please review and give feedback of any kind. hope it helps.

@editwentyone Hi, I have the same "problem", so, reading the image you sent, i need to send more coins to another jar if i want to start earning? Why another jar and not the one where the fidelity bond was created?

I think (just my 2 sats) it doesn't really matter if you re-send it to the same jar, I'm not sure about privacy implications, just use a fresh receiving address

Closing this as the next release will have a warning message that should make it more obvious (for users that have not read the docs about Fidelity Bonds). Reopen on demand.
:camera_flash:


ale#statusline#Count couldn't return a proper result

Hi, I try to integrate ale message into my own statusline function, and I found out ale#statusline#Count maybe the right method to call
below is a test code I put into init.vim (neovim)
function! LinterStatus() abort
    let l:counts = ale#statusline#Count(bufnr(''))

    let l:all_errors = l:counts.error + l:counts.style_error
    let l:all_non_errors = l:counts.total - l:all_errors

    return l:counts.total == 0 ? 'OK' : printf(
                \   '%dW %dE',
                \   all_non_errors,
                \   all_errors
                \)
endfunction

function! MyTest() abort
    let m = LinterStatus()
    echom m
endfunction

autocmd BufWinEnter,BufRead,BufReadPost,WinEnter,FileType * call MyTest()

ale plugin works perfectly, but the test script have problems
It doesn't work (print 'OK' with error files):

run nvim file_with_error.py in terminal
run :e file_with_error.py in neovim
It works:
run :vs in neovim
:w save buffer if I add BufWrite in autocmd

See :help <abuf>. bufnr('') might be returning a different buffer number. You also might be calling the function before linting has been completed.

The buffer number should be OK. I replaced with , it print the same buf number.
How should I calling the function after linting completing?
I tried autocmd User ALELint echom "ALE run!" but it didn't executed

The example in the documentation is wrong. I'll fix it so the autocmd can be used to echo things.
The autocmd is run with silent, so echo won't work.

I updated the documentation in the end to include unsilent.
autocmd User ALELint unsilent echom 'ALE run!'

It works perfectly! Thanks!

d


Add the possibility to use a pre-shared symmetric key

Add the possibility to set pre shared keys

https://github.com/angristan/wireguard-install/pull/13

From the WireGuard technical white paper:

In order to mitigate any future advances in quantum computing, WireGuard also supports a mode in which any pair of peers might additionally pre-share a single 256-bit symmetric encryption key between themselves, in order to add an additional layer of symmetric encryption. The attack model here is that adversaries may be recording encrypted traffic on a long term basis, in hopes of someday being able to break Curve25519 and decrypt past traffic. While pre-sharing symmetric encryption keys is usually troublesome from a key management perspective and might be more likely stolen, the idea is that by the time quantum computing advances to break Curve25519, this pre-shared symmetric key has been long forgotten. And, more importantly, in the shorter term, if the pre-shared symmetric key is compromised, the Curve25519 keys still provide more than sufficient protection. In lieu of using a completely post-quantum crypto system, which as of writing are not practical for use here, this optional hybrid approach of a pre-shared symmetric key to complement the elliptic curve cryptography provides a sound and acceptable trade-off for the extremely paranoid. Furthermore, it allows for building on top of WireGuard sophisticated key-rotation schemes, in order to achieve varying types of post-compromise security.

https://www.wireguard.com/papers/wireguard.pdf (5.2)

From the WireGuard technical white paper:

In order to mitigate any future advances in quantum computing, WireGuard also supports a mode in which any pair of peers might additionally pre-share a single 256-bit symmetric encryption key between themselves, in order to add an additional layer of symmetric encryption. The attack model here is that adversaries may be recording encrypted traffic on a long term basis, in hopes of someday being able to break Curve25519 and decrypt past traffic. While pre-sharing symmetric encryption keys is usually troublesome from a key management perspective and might be more likely stolen, the idea is that by the time quantum computing advances to break Curve25519, this pre-shared symmetric key has been long forgotten. And, more importantly, in the shorter term, if the pre-shared symmetric key is compromised, the Curve25519 keys still provide more than sufficient protection. In lieu of using a completely post-quantum crypto system, which as of writing are not practical for use here, this optional hybrid approach of a pre-shared symmetric key to complement the elliptic curve cryptography provides a sound and acceptable trade-off for the extremely paranoid. Furthermore, it allows for building on top of WireGuard sophisticated key-rotation schemes, in order to achieve varying types of post-compromise security.

https://www.wireguard.com/papers/wireguard.pdf (5.2)

i wanna die.

https://pics.me.me/roses-are-red-this-life-isa-existence-spain-i-just-15266613.png

I dislike that they refer to it as the "extremely paranoid" as much as the privacy-conscious at this point you are currently losing freedoms for things you say and do online people should be conscious of these things.  Saying anything on social media is one of those things that people forget that are never forgotten let alone your browsing habits.  I wonder what the dictators would be and current would say once options like WireGuard become part of the base specification of the internet infrastructure.


Topic page: Show N/A placeholder if there is not offset info available

Setup: topic page, BE returns null min/max offsets.
Current behavior: Min and Max offsets not shown, Messages count is 0 (which is invalid)
Expected:

if either max or min offsets are unknown then Messages count should show N/A
if one of offset not available, then corresponding column should have N/A values

@pranit-yawalkar sure thing, go ahead

Hye
want to work on this issue

@pranit-yawalkar any luck?

Hi, is this still open?

@JwuCode hey, yes it is.


feat: handle dssev001 tlog entry types

re: https://github.com/slsa-framework/slsa-github-generator/issues/3750
Rekor TLog entries can now be of the type dsse v0.0.1, as when what's returned when using sigstore-go's Bundle().
This is to support eventual Sigstore Bundles produced by slsa-github-generator's "generic" generator, which will likely use sigstore-go's Bundle to produce attestations

https://github.com/slsa-framework/slsa-github-generator/compare/main...ramonpetgrave64-internal-builder-sigstore-bundlev2#diff-b186a0c5d9ae459b11b694f05455568453699670926d21cad06cafec3dbf895eR101
https://github.com/slsa-framework/slsa-github-generator/actions/runs/10359750833

Tesing

Added unit tests with stub data
manual invocations to very both new and old attestations and bundles, with some modifications for testing purposes

https://github.com/slsa-framework/slsa-verifier/compare/main...verify-sigstore-go-Bundlev3#diff-94741068472ee694a12811cd704179dd478a9fa20a3bf45cf6ea2d4406214dc2R179

Followup
Finish the work to produce bundles from the generic generators

https://github.com/slsa-framework/slsa-github-generator/compare/main...ramonpetgrave64-internal-builder-sigstore-bundlev2#diff-b186a0c5d9ae459b11b694f05455568453699670926d21cad06cafec3dbf895eR101

@cmurphy, please take a look

@haydentherapper We can't yet because for the older attestations produce by slsa-github-generator, the certificate was not embedded within the envelope.
But that seems like another good reason for https://github.com/slsa-framework/slsa-verifier/issues/487


[New chain]: Chronicle Yellowstone

Chain Name
Chronicle Yellowstone - Lit Protocol Testnet
RPC URL
https://yellowstone-rpc.litprotocol.com
The chain must be added to https://chainlist.org/

[X] I confirm that the chain is added to chainlist

After creating the issue, a bot will estimate the required pre-fund and post it in the comments. Please check this checkbox after you send the pre-fund.

[ ] I sent the pre-fund in accordance with Github Action's comment

Relevant information
Block explorer: https://yellowstone-explorer.litprotocol.com/

Sent!  https://yellowstone-explorer.litprotocol.com/tx/0xd2051edec5c9dace743fe37119bf154819831143f1eeb8c8e97b8855456aebcc


Feature/issue 31 wait after trick

New Features

adds 'ready for trick' checkin event to wait before dealing the next trick

@areisle I think i found a bug, when a new trick started the leader was for the current trick and not the upcoming one


"_" type with @sortBy directive does not work with @paginate lighthouse directive

Hi,
when I use @sortBy (or @searchBy) with auto generated type "_", I get error:
Impossible to create Sort Clause for `type CategoryPaginator`

with @all directive, everything works fine. Seems like @sortBy and @searchBy does not support paginators.

The @searchBy directive is not yet supported _, the @sortby should work now.


Backport: TF Can delete read only settings and rbac TF

Backport: https://github.com/rancher/rancher/issues/19825

Able to reproduce the issue with v2.2.2. We are allowed to delete cacerts.
Tested with v2.2.3-rc9.
When attempting to delete cacerts, user is presented with "405 MethodNotAllow" error .
HTTP/1.1 DELETE /v3/settings/cacerts
Host: x.x.x
Accept: application/json

HTTP Response:
HTTP/1.1 405
date: Sat, 11 May 2019 03:19:43 GMT
content-encoding: gzip
x-api-schemas: https://x.x.x/v3/schemas
content-type: application/json
content-length: 129
expires: Wed 24 Feb 1982 18:42:00 GMT

{
"baseType": "error",
"code": "MethodNotAllow",
"message": "Cannot delete readOnly setting cacerts.",
"status": 405,
"type": "error"
}


Changed aka.ms url to use https

Use https on aka.ms link for better security
Issue:
Url shortener should be called with https instead of http
Reason:
Redirect to https could be hijacked - explicit https is better practice
Fix:
changed url from http to https
Validation:

completed in 810a4a49bce5df5da8e7e824eedee11c4450751b. Not sure why your commit had something additional, which is why i didn't merge it.


Bad formatting with aligned iterable operations

The formatter doesn't deal nicely with well-aligned iterable operations as in the following examples:
===
    statics.addAll(elements
        .where((e) => e is FunctionElement)
        .where((e) => universe.staticFunctionsNeedingGetter.contains(e))
        .map(_buildStaticMethodTearOff));
    List<Class> classes = elements
        .where((e) => e is ClassElement)
        .map(_buildClass)
        .toList(growable: false);
===
It currently produces:
    statics.addAll(
        elements.where(
            (e) =>
                e is FunctionElement).where(
                    (e) =>
                        universe.staticFunctionsNeedingGetter.contains(
                            e)).map(_buildStaticMethodTearOff));
    List<Class> classes =
        elements.where(
            (e) => e is ClassElement).map(_buildClass).toList(growable: false);

This issue has been moved to dart-lang/dart_style#271.


Testing, please ignore. (pwrtje)

Bug bounty test - please ignore.... Please DO NOT APPROVE THIS! (pwrtje)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.aviluzgalnome seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


fix for uploading jpg & png

Purpose

Updating default config to allow uploading jpg & png formats
Fixes #283

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

Heya! Changes look good. How does the layout loading and chunking strategy handle the images? Have you tested this with multiple images? Thanks!

Yes I tested with couple of images and it worked fine. Loading strategy as Layout uses the Layout model for Document Intelligence (Azure Form Recognizer) which can parse images (extracting text) and the Chunking strategy as Layout then chunks the text as it would for a PDF


Failed to find package hdl_localization

Hi,@koide3,
When I run " roslaunch hdl_people_tracking hdl_people_tracking.launch ",the following error occurs.
... logging to /home/jintaiyu/.ros/log/9cdcaf3c-f88f-11e8-b306-000ec6a10ce2/roslaunch-jintaiyu-MIIX-510-12ISK-7362.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
Traceback (most recent call last):
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/init.py", line 307, in main
p.start()
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/parent.py", line 268, in start
self._start_infrastructure()
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/parent.py", line 217, in _start_infrastructure
self._load_config()
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/parent.py", line 132, in _load_config
roslaunch_strs=self.roslaunch_strs, verbose=self.verbose)
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/config.py", line 451, in load_config_default
loader.load(f, config, verbose=verbose)
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 746, in load
self._load_launch(launch, ros_config, is_core=core, filename=filename, argv=argv, verbose=verbose)
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 718, in _load_launch
self._recurse_load(ros_config, launch.childNodes, self.root_context, None, is_core, verbose)
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 682, in _recurse_load
val = self._include_tag(tag, context, ros_config, default_machine, is_core, verbose)
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 95, in call
return f(*args, **kwds)
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 587, in _include_tag
inc_filename = self.resolve_args(tag.attributes['file'].value, context)
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 183, in resolve_args
return substitution_args.resolve_args(args, context=context.resolve_dict, resolve_anon=self.resolve_anon)
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/substitution_args.py", line 316, in resolve_args
resolved = _resolve_args(resolved, context, resolve_anon, commands)
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/substitution_args.py", line 329, in _resolve_args
resolved = commands[command](resolved, a, args, context)
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/substitution_args.py", line 142, in _find
source_path_to_packages=source_path_to_packages)
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/substitution_args.py", line 188, in _find_executable
full_path = _get_executable_path(rp.get_path(args[0]), path)
File "/usr/lib/python2.7/dist-packages/rospkg/rospack.py", line 203, in get_path
raise ResourceNotFound(name, ros_paths=self._ros_paths)
ResourceNotFound: hdl_localization
ROS path [0]=/opt/ros/indigo/share/ros
ROS path [1]=/home/jintaiyu/catkin_ws6/src
ROS path [2]=/opt/ros/indigo/share
ROS path [3]=/opt/ros/indigo/stacks
But I have added the package path of hdl_localization(/home/jintaiyu/catkin_ws5/src) to ROS_PACKAGE_PATH and also added hdl_localization_DIR to Cmakelists.txt,the error still exists.
Can you give me some directions about this problem?
Sincerely
ikunjin

Hi @ikunjin ,
Does "source /your/catkin_ws/devel/setup.bash && roscd hdl_people_tracking" work?

I have the same problem - any help?


How to get il2cpp functions?

Hi :-)
I was previously using the JSON output from IL2CPPInspector, but as this project is deprecated, I need to think about what I will use going forward.
While CPP2IL doesn't support JSON output, I could imagine adding that myself.
However, what I currently don't see, is a way to get il2cpp functions like
il2cpp_array_new
il2cpp_value_box
il2cpp_object_new
Which I currently need for my project.
How would I get the pointers to these functions, with Cpp2IL?
For Context: I need these pointers for an Cpp dll injection project, that does runtime hooking to these pointers.

Those functions are just exported from the binary. you could simply iterate over the exports.

So they would be part of
LibCpp2IlGlobalMapper.MethodRefs ?

No.

Can you give me a hint where I need to look then?
Sry, I'm not that deep into how the whole il2cpp metadata works, so I have trouble finding it myself.

They're not in metadata. They're ordinary binary exports, unrelated to anything IL2CPP.

Ah, now I understand.
Is there anything in cpp2il already, that can parse the exports?
If not, it looks like IL2CPPInpsector has some code for that, I guess I could just port that over.

you can simply get their pointers with GetProcAddress

you can simply get their pointers with GetProcAddress

No you can't.

Is there anything in cpp2il already, that can parse the exports?

Exports are already parsed, Il2CppBinary base class has methods related to getting them by name.

Awesome. That was the hint I needed. Thanks a lot :-)
I can now try to write a JSON export, with the data I need.


Update license headers and template to 2022

A good chance to standardize all to use # instead of triple quotes!


[Theme Switching Migration] Auth2FA Batch

Part of https://github.com/Expensify/App/issues/31677
As part of the Theme Switching Project, we need to migrate the following:

[ ] AnimatedStep/index.js
[ ] OfflineIndicator.js
[ ] PressableWithDelayToggle.tsx
[ ] GenericPressable/BaseGenericPressable.tsx (is used in PressableWithDelayToggle)

leaving a comment to be assigned :)

Hello!
I'm Krzysztof from Callstack - an expert contributor group and I would like to work on this one.

@grgia Can you please assign me here?

@mountiny please add @keisyrzk to the Contractors list 🙂 Melvin doesn't know yet he's from Callstack

Made a PR for that

hey @miljakljajic  could you help me out with the $500 C+ review payment to @s77rt?

contract sent @s77rt !

@miljakljajic Accepted! Thanks!

Paid! Thank you for your work @s77rt
Seems like @keisyrzk and @koko57 are both from callstack, so are we good to close - no further payments?


gcc4.7 build failed in default_health_check_service.cc

src/cpp/server/health/default_health_check_service.cc: In constructor ‘grpc::DefaultHealthCheckService::DefaultHealthCheckService()’:
src/cpp/server/health/default_health_check_service.cc:135:17: error: ‘class std::map<std::basic_string<char>, bool>’ has no member named ‘emplace’

gcc version 4.7.2
This issue can be solved with this patch:
diff --git a/src/cpp/server/health/default_health_check_service.cc b/src/cpp/server/health/default_health_check_service.cc
index bc98ce7..a866af9 100644
--- a/src/cpp/server/health/default_health_check_service.cc
+++ b/src/cpp/server/health/default_health_check_service.cc
@@ -131,7 +131,7 @@ Status DefaultHealthCheckService::HealthCheckServiceImpl::Check(
 }

 DefaultHealthCheckService::DefaultHealthCheckService() {
-  services_map_.emplace("", true);
+  services_map_[""] = true;
 }

 void DefaultHealthCheckService::SetServingStatus(

Is this emplace important here? Can we use [] syntax to fix gcc 4.7 build?

I am okay changing it to [ ]. Do you want to send a PR? Or I can do it. Thanks.

I can believe that at the current time, no other features will fail on 4.7 . However: we are no longer claiming to support 4.7 as it doesn't support c++11 . The first gcc to support c++11 is 4.8 and that is our expected minimum. As we increase usage of c+11 features (in particular, certain memory model details that were first supported in 4.8), the code will no longer work on 4.7.

Do you want to send a PR? Or I can do it.

Can you do it, please?

As we increase usage of c+11 features (in particular, certain memory model details that were first supported in 4.8), the code will no longer work on 4.7.

Makefile has a detection of C++11 (grep by HAS_CXX11). I guess all those C++11 features we are going to use have C++03 alternatives that can be supported by conditional compilation.

We should probably remove that check since we've been requiring C++11 since version 1.1 . We don't use the results anymore except for setting the -std=c++11 flag , and we no longer support alternatives like we used to (for example, the fake nullptr that used to live in include/grpc++/impl/codegen/config.h )

Boris, as @vjpai mentioned we are no longer supporting pre-C++11 compilers. While making the change may re-enable the build for you, it can and will break at any time. After discussions I am not going to create the PR and you may want to make a local fork or pin to an earlier release to continue using 4.7. Thanks.


fix for 0.6.1

Thank you for contribution, could you please remove the .DS_Store file. Then I will gladly merge your PR.


pygit2: fix posixpath conversion from windows on is_ignored

When we were converting windows path to posixpath, the values
were not in effect because we were not setting it to the
variable.
Also fixes #11, which unskips  on Windows + pygit2 backend, which
was due to the above bug.

Test failures are unrelated, see #27.


heroku cloud 9 terminal command is incorrect, I think.

Challenge http://freecodecamp.com/challenges/waypoint-get-set-for-basejumps has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
~/workspace/dist && heroku config:set NODE_ENV=production && heroku addons:create mongolab
is should be:
~/workspace/dist && heroku config:set NODE_ENV=production && heroku addons:add mongolab
not "create" should be "add"

No, create is deprecated.
Check: https://devcenter.heroku.com/articles/managing-add-ons
specifically this line:
"Previously to add an add-on you could use the command addons:add. That is now deprecated in favor of the create command."

Then why do i an error? Add worked create said not a valid heroku command
-------- Original Message --------
Subject: Re: [FreeCodeCamp] heroku cloud 9 terminal command is incorrect, I think. (#3080)
From: "Jon Lucas"<EMAIL_ADDRESS>Date: Sat, September 5, 2015 9:32 am
To: "FreeCodeCamp/FreeCodeCamp"<EMAIL_ADDRESS>CC: "Albert Ventura"<EMAIL_ADDRESS>No, create is deprecated.
Check: https://devcenter.heroku.com/articles/managing-add-ons
specifically this line:
"Previously to add an add-on you could use the command addons:add. That is now deprecated in favor of the create command."

Reply to this email directly or view it on GitHub:
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/3080#issuecomment-137972850

@venturads What is the error that you are getting?

In c9 it says that create is not a valid heroku command and when I do heroku help addons its doesn't list create only add
-------- Original Message --------
Subject: Re: [FreeCodeCamp] heroku cloud 9 terminal command is incorrect, I think. (#3080)
From: "Jon Lucas"<EMAIL_ADDRESS>Date: Sat, September 5, 2015 11:42 am
To: "FreeCodeCamp/FreeCodeCamp"<EMAIL_ADDRESS>CC: "Albert Ventura"<EMAIL_ADDRESS>@venturads What is the error that you are getting?

Reply to this email directly or view it on GitHub:
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/3080#issuecomment-137985788

@venturads  The problem here is that the heroku package is more than likely out of date.  If you run: heroku version  you'll more than likely see 3.31.x.  When you run heroku help addons do you see this line:
WARNING: Toolbelt v3.41.5 update available.?
If you do, run this line in the console:
wget -O- https://toolbelt.heroku.com/install-ubuntu.sh | sh
which will update the toolbelt to the latest version.  You'll then see the changes to the heroku help addons command.
I find out of date versions to be the common issue with cloud9.  For instance, node.js is version 0.10.x not 0.12.x which is the current stable release.  The default npm is similarly out of date, for what it's worth.

is there any list of latest version and how to update them?Thank you,Albert Ventura909-810-3512
-------- Original Message --------
Subject: Re: [FreeCodeCamp] heroku cloud 9 terminal command is
incorrect, I think. (#3080)
From: Jon Lucas<EMAIL_ADDRESS>Date: Sat, September 05, 2015 12:12 pm
To: FreeCodeCamp/FreeCodeCamp<EMAIL_ADDRESS>Cc: Albert Ventura<EMAIL_ADDRESS>@venturads The problem here is that the heroku package is more than likely out of date. If you run: heroku version you'll more than likely see 3.31.x. When you run heroku help addons do you see this line: WARNING: Toolbelt v3.41.5 update available.? If you do, run this line in the console: wget -O- https://toolbelt.heroku.com/install-ubuntu.sh | sh which will update the toolbelt to the latest version. You'll then see the changes to the heroku help addons command. I find out of date versions to be the common issue with cloud9. For instance, node.js is version 0.10.x not 0.12.x which is the current stable release. The default npm is similarly out of date, for what it's worth. —Reply to this email directly or view it on GitHub.

Thanks that worked, i updated my toolbelt.  When I push new commits to heroku: $ grunt --force && grunt buildcontrol:herokubut i get another error: "  GET /api/thingsMongoDB connection error: MongoError: connect ECONNREFUSED"
-------- Original Message --------
Subject: Re: [FreeCodeCamp] heroku cloud 9 terminal command is
incorrect, I think. (#3080)
From: Jon Lucas<EMAIL_ADDRESS>Date: Sat, September 05, 2015 12:12 pm
To: FreeCodeCamp/FreeCodeCamp<EMAIL_ADDRESS>Cc: Albert Ventura<EMAIL_ADDRESS>@venturads The problem here is that the heroku package is more than likely out of date. If you run: heroku version you'll more than likely see 3.31.x. When you run heroku help addons do you see this line: WARNING: Toolbelt v3.41.5 update available.? If you do, run this line in the console: wget -O- https://toolbelt.heroku.com/install-ubuntu.sh | sh which will update the toolbelt to the latest version. You'll then see the changes to the heroku help addons command. I find out of date versions to be the common issue with cloud9. For instance, node.js is version 0.10.x not 0.12.x which is the current stable release. The default npm is similarly out of date, for what it's worth. —Reply to this email directly or view it on GitHub.

@venturads That error is part of the default tests built into the default api endpoints.  If you were to be running your server at the time that those tests were run, you probably wouldn't see that error.  If you want to explore testing more you can look at the *.spec.js files.  Glad things otherwise got worked out for you!  You might find better help regarding other errors you might encounter in the chat.  Feel free to reach out to me there too.

@venturads Please close this issue if it's resolved. Please don't keep a hanging issue.


use six.u for unicode encoding

Quick fix for #81
Since utf is widely used and will inevitably come up while interacting via socketIO, using six.u fixes the problem. The method is detailed here

Thanks @kengz, but this fix does not work in Python 3.


fix fx rounding error for tiny amounts

This was a pretty big oops for us, specifically when a client was trying to convert between SLL and USD. The effective exchange rate was coming back as '0.0' because the numerator was an integer rather than a float.

Hi @zapnap, thanks for the fix!


Update request: lfe 1.3 → 2.1.1

Package name: lfe (Lisp Flavored Erlang)
Latest released version: 2.1.1

Current version on the unstable channel: 1.3
Current version on the stable/release channel: 1.3

[X] Checked the nixpkgs pull requests

Notify maintainers

Note for maintainers: Please tag this issue in your PR.

@f3zhead Please test. Tracking: https://nixpk.gs/pr-tracker.html?pr=222411
But you can use nixpkgs-review too.
At nixpkgs git directory:

nix run github:mic92/nixpkgs-review pr 222411


Need Configuration file in component

Here json configuration file will be required in Component
component,json
structure like
{
    "name": "name",
    "id": "folder/dir_name",
    "version": "1.0.0",
    "zversion": "3.0.0",
    "status": true,
    "license": "license",
    "author": {
            "name": "name",
            "email":"email",
            "homepage": "website"
    }
}

The codacy quality service is failed.
Could you check that before merging PR?

@peter279k  so what you think

@peter279k  i deleted the app codacy

Hi @Lablnet, I think it's fine to do that I think.
At this moment, the test and features are more important than code quality.

Yes and also codacy says use of file_exists function is discourage like that useless errors i dont know why


Report Performance and Throughput as Rates

Is your feature request related to a problem? Please describe.
As a user, Would like TS to support sending throughput rates with dimensions natively (vs. custom endpoints) as Cloud Scaling Policies can usually only act on rates (not counters) and throughput is one of the most common performance metrics one needs.  In general, would like to be as surgical as possible and only send metrics I am leveraging (ex. CPU + Throughput).
Current Config:
{
   "class": "Telemetry",
   "controls": {
      "class": "Controls",
      "logLevel": "debug"
   },
   "My_Metrics_Namespace": {
      "class": "Telemetry_Namespace",
      "My_System_Poller": {
         "class": "Telemetry_System_Poller",
         "interval": 60,
         "actions": [
            {
               "includeData": {},
               "locations": {
                  "system": {
                     "cpu": true
                  }
               }
            }
         ]
      },
      "My_Scaling_Endpoints": {
         "class": "Telemetry_Endpoints",
         "items": {
            "throughputIn": {
               "name": "throughputIn",
               "path": "/mgmt/tm/sys/performance/throughput?$top=1&$select=Current"
            },
            "system": {
               "name": "hostname",
               "path": "/mgmt/tm/sys/global-settings?$select=hostname"
            }
         }
      },
      "My_Custom_Endpoints_Poller": {
         "class": "Telemetry_System_Poller",
         "interval": 60,
         "endpointList": [
            "My_Scaling_Endpoints/throughputIn",
            "My_Scaling_Endpoints/system"
         ]
      },
      "My_Telemetry_System": {
         "class": "Telemetry_System",
         "systemPoller": [
            "My_System_Poller",
            "My_Custom_Endpoints_Poller"
         ]
      },
      "My_Cloudwatch_Metrics": {
         "class": "Telemetry_Consumer",
         "type": "AWS_CloudWatch",
         "region": "{{{ REGION }}}",
         "dataType": "metrics",
         "metricNamespace": "bigip-scaling-test-3"
      }
   },
   "My_Remote_Logs_Namespace": {
      "class": "Telemetry_Namespace",
      "My_Listener": {
         "class": "Telemetry_Listener",
         "port": 6514
      },
      "My_Cloudwatch_Logs": {
         "class": "Telemetry_Consumer",
         "type": "AWS_CloudWatch",
         "region": "{{{ REGION }}}",
         "logGroup": "f5telemetry",
         "logStream": "f5-waf-logs"
      }
   }
}

which does not send dimensions for custom endpoints (ex. even though include the required or recommended hostname?)
            "system": {
               "name": "hostname",
               "path": "/mgmt/tm/sys/global-settings?$select=hostname"
            }

NOTE: This may just be a bug?
But desired end functionality is just to be able to include performance/throughput without custom endpoints as it's very common use case/metric:
{
   "My_System_Poller": {
      "class": "Telemetry_System_Poller",
      "interval": 60,
      "actions": [
         {
            "includeData": {},
            "locations": {
               "system": {
                  "cpu": true,
                  "performance": true, // <- NEW RFE
               }
            }
         }
      ]
   }
}

NOTE: Below is required to send dimensions for CPU:
{
   "My_System_Poller": {
      "class": "Telemetry_System_Poller",
      "interval": 60,
      "actions": [
         {
            "includeData": {},
            "locations": {
               "system": {
                  "cpu": true,
                  "hostname": true,
                  "machineId": true,
                  "version": true,
                  "versionBuild": true,
                  "platformId": true,
                  "chassisId": true,
                  "baseMac": true
               }
            }
         }
      ]
   }
}

So if this is needed, to get cpu + throughput with dimensions., may need:
{
   "My_System_Poller": {
      "class": "Telemetry_System_Poller",
      "interval": 60,
      "actions": [
         {
            "includeData": {},
            "locations": {
               "system": {
                  "cpu": true,
                  "hostname": true,
                  "performance": true // <-- NEW RFE
                  "machineId": true,
                  "version": true,
                  "versionBuild": true,
                  "platformId": true,
                  "chassisId": true,
                  "baseMac": true
               }
            }
         }
      ]
   }
}

Describe alternatives you've considered
To get dimensions for the custom endpoints, even tried to replicate fields in above include
{
   "My_Scaling_Endpoints": {
      "class": "Telemetry_Endpoints",
      "items": {
         "throughputIn": {
            "name": "throughputIn",
            "path": "/mgmt/tm/sys/performance/throughput?$top=1&$select=Current"
         },
         "hostname": {
            "name": "hostname",
            "path": "/mgmt/tm/sys/global-settings?$select=hostname"
         },
         "machineId": {
            "name": "machineId",
            "path": "/mgmt/shared/identified-devices/config/device-info?$select=machineId"
         },
         "version": {
            "name": "version",
            "path": "/mgmt/shared/identified-devices/config/device-info?$select=version"
         },
         "versionBuild": {
            "name": "versionBuild",
            "path": "/mgmt/shared/identified-devices/config/device-info?$select=build"
         },
         "platformId": {
            "name": "platformId",
            "path": "/mgmt/shared/identified-devices/config/device-info?$select=platform"
         },
         "chassisId": {
            "name": "chassisId",
            "path": "/mgmt/shared/identified-devices/config/device-info?$select=chassisSerialNumber"
         },
         "baseMac": {
            "name": "baseMac",
            "path": "/mgmt/shared/identified-devices/config/device-info?$select=baseMac"
         }
      }
   }
}

But no dice.
However, in the end, would really just like to avoid needing custom endpoints altogether as a really common metric/use case.

Thank you for your feedback. I have added AUTOTOOL-2492 to our internal product backlog to expose throughput data with the default system poller.

This was resolved with the 1.23.0 release of Telemetry Streaming.


Multiple Microsoft.Authorization types missing

Bicep version
Bicep CLI version 0.5.6 (5f2f88f0f0)
Describe the bug
Following types return warning message as having no types available BCP081:

Microsoft.Authorization/roleAssignments@2021-04-01-preview
Microsoft.Authorization/roleDefinitions@2018-07-01

To Reproduce
https://github.com/Azure/azure-quickstart-templates/blob/9583713c102dff5c95eec73ad38db579db051bfb/demos/imagebuilder-windowsbaseline/main.bicep#L92-L100
https://github.com/Azure/azure-quickstart-templates/blob/9583713c102dff5c95eec73ad38db579db051bfb/demos/imagebuilder-windowsbaseline/main.bicep#L57-L64
From my own template in VS Code showing the warning:

Lot's of "new" warnings from old templates here. Same with newer version (0.7.4)
For roleDefinitions only 2018-01-01-preview and 2015-07-01 showing up..

@matsest -- are you saying the warnings are showing up for the first time w/ v0.7.4? Or have they always been there?

@alex-frankel - I don't have the CLI versions to go through this installed, but. e.g. with Bicep 0.7.4 these are the only two suggested from intellisense (which matches what can be found on the published docs at the moment):

while in previous versions like here (0.3.1) https://github.com/Azure/bicep/issues/2086 there were a number of other valid versions:

The resource type 'roleDefinitions' could not be found in the namespace 'Microsoft.Authorization' for api version '2020-03-01-preview'.
The supported api-versions are '2014-04-01-preview,2014-07-01-preview,2014-10-01-preview,2015-05-01-preview,2015-06-01,2015-07-01,2016-07-01,2017-05-01,2017-09-01,2018-01-01-preview,2018-07-01'.

To be fair, most Microsoft.Authorization resources haven't been passing Bicep builds cleanly (without warning) in general, and I'm guessing it's not due to Bicep itself but rather in the published resource provider specs. But since it is such a important/widely used RP it would be great if the Bicep team could follow up this internally with the relevant RP team :)

+1 on the message from @matsest
This provider has been reported numerous times in the "provider types mega-thread",
Combined with ARM-TTK you can chose between having the types missing error, or invalid arm-ttk tests.

@jeskew / @anthony-c-martin -- any idea why w/ an older version of bicep, we would have had more recent api versions than the ones we have available now?

@alex-frankel The 2020-03-01-preview version of authorization was removed from the Azure swagger repo in https://github.com/Azure/azure-rest-api-specs/pull/13786. From the bug report in #2086, it sounds like that API version was not recognized by the resource provider. I ran a search over the swagger for any Microsoft.Authorization/roleDefinitions resources we might be missing, but it looks like 2015-07-01 and 2018-01-01-preview are being correctly identified as the only versions available:

A similar search for Microsoft.Authorization/roleAssignments is not pulling anything up under the 2021-04-01-preview version (though 2020-04-01-preview is a valid version for that resource).
I think the quickstarts may need to be updated? The versions used in the issue description look like typos to me.

@matsest / @ReneRebsdorf -- thoughts on this? Have you been able to successfully call those newer API versions?

Yes, using those two versions will remove the warnings. But still lots of quickstarts and templates uses other versions and throws warnings.
I think this is still the real issue here:

The Resource Explorer in the Azure portal does report that the versions used in the quickstarts exist; the swagger documents just need to be updated to reflect what is deployed.

@alex-frankel
The problem with this, is that it causes problems with ARM-TTK:
´´´ text
Api versions must be the latest or under 2 years old (730 days) - API version 2018-01-01-preview of Microsoft.Authorization/roleDefinitions is 1634 days old Line: 14, Column: 8
Valid Api Versions:
2018-07-01
2018-07-01
´´´
The api versions all seem to work, but there are alignment issues between biceps type support, arm-ttks valdiation, and the versions exposed on the RP's swagger.
If the three were aligned I'd be a happy camper.

api versions all seem to work

Have you verified that the deployments are successful with these API versions? Because if they are, then bicep & swagger are wrong, and TTK is actually telling you the right thing :) Our understanding is that these API versions are not actually available to use.

Sorry, that was very unfortunate phrasing on my part.
What I meant was that while they may work, the types noise still exists.
If types were available for 2018-07-01, it seems everything falls in place.

I am still confused.. :) Here is the situation as I understand it:

at one point, the newer types were available in bicep, but we determined those APIs were not actually available (at least not in all regions)
as a result of that discovery, the Authorization RP team removed those more recent types from the azure-rest-api-specs, which subsequently removed them from bicep.

If you are confident that the more recent API versions are working, then the next step will be to ask the Auth RP team to add those specs back
Have you successfully deployed end-to-end with these more recent types? (meaning, everything works beyond the warning in bicep).

@alex-frankel
The below bicep template works with targetScope managementGroup and subscription. Tested for Create and Update
It gives: "Resource type "Microsoft.Authorization/roleDefinitions@2018-07-01" does not have types available."
2018-07-01 is missing as per your previous comment from docs
But it is the only accepted version in ARM-TTK as per my previous comment.
targetScope = 'managementGroup'

param targetMg string

resource NetOps 'Microsoft.Authorization/roleDefinitions@2018-07-01' = {
  name: '0015fc97-aa54-4497-b825-bc782b1872f8'
  properties: {
    roleName: 'Network management (NetOps)'
    description: 'Platform-wide global connectivity management: Virtual networks, UDRs, NSGs, NVAs, VPN, Azure ExpressRoute, and others'
    type: 'customRole'
    permissions: [
      {
        actions: [
          '*/read'
          'Microsoft.Network/*'
          'Microsoft.Resources/deployments/*'
          'Microsoft.Support/*'
        ]
      }
    ]
    assignableScopes: [
      '/providers/Microsoft.Management/managementGroups/${targetMg}'
    ]
  }
}

any news on this?


Only render updated items in an array

I have an array of items in Zustand store, and if I update one, all items in the array rerender.
I have a simple example here where a store has a list of colors rendered to divs. When you click on a div it updates the items in the stored array. However, all items rerender when one is changed. Is there a way to set up Zustand so only one object rerenders when it item changes in an array?
https://codesandbox.io/s/polished-framework-59eys
import React from "react";
import ReactDOM from "react-dom";
import produce from "immer";
import create from "zustand";

export const immer = config => set => {
  return Object.entries(config()).reduce(
    (acc, [key, value]) => ({
      ...acc,
      [key]:
        typeof value === "function"
          ? (...args) => set(produce(draft => void config(draft)[key](...args)))
          : value
    }),
    {}
  );
};

const store = state => ({
  divs: ["red", "red", "red"],
  updateColor: (color, index) => {
    state.divs[index] = color;
  }
});

const [useStore] = create(immer(store));

const App = () => {
  const { divs } = useStore();
  return (

      {divs.map((d, i) => (
        <DivEl color={d} index={i} />
      ))}

  );
};

const DivEl = ({ color, index }) => {
  const { updateColor } = useStore();
  return (

 updateColor(color === "red" ? "blue" : "red", index)}
      style={{
        width: "100px",
        height: "100px",
        background: color,
        margin: "1em"
      }}
    />
  );
};

const rootElement = document.getElementById("root");
ReactDOM.render(<App />, rootElement);

I think it might be because you don't have a key on each element. React uses keys to know which item has changed or has been removed/added to the list. Without a stable identity, it doesn't know and renders everything again.

  {divs.map((d, i) => (
-    <DivEl color={d} index={i} />
+    <DivEl color={d} index={i} key={i} />
  ))}

Now using indexes as keys is not always good, it depends if the items in the list will have their order changed eventually. In that case you might need something that is uniquely tied up to each item.

Sorry, that was clumsy of me, but the keys don't make a difference. I've updated the codesandbox above and all items still rerender when only one item has changed.

Sorry I got confused as well :). Not having stable keys would actually force React to destroy and create items on each render pass because it doesn't know which items got updated/added/removed since the keys are different (or no keys at all).
The fact that all DivEl re-renders is normal because it's parent re-renders due to the Divs state slice to update in the store. To avoid unnecessary renders, we can leverage memo which would do a shallow equal comparison on the props and abort rendering if they haven't changed.
I forked your sandbox and used memo: https://codesandbox.io/s/musing-curran-gwnor

Perfect, that does the trick! Thankyou!


Bad generation after training/finetuning

We train the model using our own dataset following the instruction provided in this repo and the token accuracy is very high and the loss is relatively low. However, after creating the pytorch_model.bin using the provided python code, the text generation is very bad, it is like some random words coming after each other. I wonder if anyone else has similar issue or if the developers have any clue on the possible reasons. Thanks.

Hi @dardodel, thank you for your question. We have updated our training scripts and the performance of the trained model should be largely improved. Could you try to use the new code provided and give us some feedback? Thanks!

@yxuansu Thanks for your response and I tried the new code but still same problem. I also double checked the requirements and we have same environment (hopefully). One thing that I paid more attention to is that when we load the trained model (the one that we finetuned and converted to pytorch_model.bin) we get this warning message, while we don't when we load publishe OpenAlpaca model. Note that the message is way longer than this and I only copied a part of it. I can copy the whole message if needed.
"Some weights of the model checkpoint at ./ckpt/openalpaca_7b/7bt_preview were not used when initializing LlamaForCausalLM: ['model.model.layers.13.self_attn.rotary_emb.inv_freq', 'model.model.layers.13.post_attention_layernorm.weight', 'model.model.layers.2.post_attention_layernorm.weight', 'model.model.layers.13.mlp.up_proj.weight', 'model.model.layers.3.mlp.up_proj.weight', 'model.model.layers.31.self_attn.q_proj.weight',
....,
....,

**This IS expected if you are initializing LlamaForCausalLM from the checkpoint of a model trained on another task or with another architecture (e.g. initializing a BertForSequenceClassification model from a BertForPreTraining model).

This IS NOT expected if you are initializing LlamaForCausalLM from the checkpoint of a model that you expect to be exactly identical (initializing a BertForSequenceClassification model from a BertForSequenceClassification model).

Some weights of LlamaForCausalLM were not initialized from the model checkpoint at ./ckpt/openalpaca_7b/7bt_preview and arenewly initialized:** ['model.layers.1.post_attention_layernorm.weight', 'model.layers.8.self_attn.rotary_emb.inv_freq', 'model.layers.14.post_attention_layernorm.weight', 'model.layers.20.self_attn.k_proj.weight',
....
...."

@dardodel Hello. I'm sorry for not getting back to you sooner. After reading your warning about loading the parameters, I noticed that the names of the parameters in your fine-tuned checkpoints begin with the prefix model.model, but the names of these parameters start with the prefix model.. Thus, you didn't load the model parameters successfully, and the random initialized parameters are used for the inference.
This problem could be fixed by running the make_shards.py scripts, which are described in the README.md carefully. Could you please follow the tutorial in README.md and run the make_shards.py script to generate the huggingface version checkpoint that can be directly loaded successfully?

@chenhl0810 Sorry for the late response. It is not correct because the size should be 7B for the OpenLLaMa-7B model.

Thanks for your reply.
Could you help to confirm that the setting of OpenLLaMa-7B is set in this file, as shown as the figure below ?

Hi @chenhl0810, thank you for spotting this! This is actually a typo (it is our trained openalpaca model). We have made corrections to the scripts, pointing to the correct OpenLLaMA checkpoints.

@dardodel Hello. I'm sorry for not getting back to you sooner. After reading your warning about loading the parameters, I noticed that the names of the parameters in your fine-tuned checkpoints begin with the prefix model.model, but the names of these parameters start with the prefix model.. Thus, you didn't load the model parameters successfully, and the random initialized parameters are used for the inference.
This problem could be fixed by running the make_shards.py scripts, which are described in the README.md carefully. Could you please follow the tutorial in README.md and run the make_shards.py script to generate the huggingface version checkpoint that can be directly loaded successfully?

@gmftbyGMFTBY
Thanks for your response. But I did nothing other than the instruction provided in the readme. After finetuning with DeepSpeed, I ran the zero_to_fp32.py to get the pytorch version of weights. My assumption was that this bin file is enough and the sharding step is just optional in case we want to break down the pytorch_model.bin into smaller pieces. Now, do I have to run the sharding? Thanks.

Hi @dardodel, may I kindly ask have you experimented with our newly updated codebase? It would be great if you can try the new codebase and I think the sharding step is not necessary once you already have a large and unified pytorch.bin file.

Hi @dardodel, may I kindly ask have you experimented with our newly updated codebase? It would be great if you can try the new codebase and I think the sharding step is not necessary once you already have a large and unified pytorch.bin file.

Yes, I tried the new code as well. The warning message I shared above was from the new code.

This is kinda strange.  I just rerun on my side the code seems to work fine. Can you run the sharding operation to see what happens?


"--encrypt-format-all" parameter in AzCli  resutls in UUIDs of the disks being changed

The --encrypt-format-all parameter will also cause the UUIDs to be changed post encryption, therefore adding the disks into the /etc/fstab with UUIDs before encryption will most likely result in a "no boot" situation for that VM due to wrong UUID. Removing that parameter allows the system keeping the same UUIDs. Please have this tested on your own end.
Before encryptiong the data disk:
/dev/sda2: UUID="3c11fba3-32c7-4d0c-b614-aad5630504eb" TYPE="xfs"
/dev/sda1: UUID="ca02dd2d-a91b-4fb1-b24b-0fb19c18b89d" TYPE="xfs"
/dev/sdb1: UUID="d4de616e-7a99-4904-9a4d-9cae793e2f9f" TYPE="ext4"
/dev/sdc1: UUID="62afbe50-54dc-4d73-a46b-36ab52c5017d" TYPE="ext4"
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
fd0      2:0    1    4K  0 disk
sda      8:0    0   32G  0 disk
├─sda1   8:1    0  500M  0 part /boot
└─sda2   8:2    0 31.5G  0 part /
sdb      8:16   0    7G  0 disk
└─sdb1   8:17   0    7G  0 part /mnt/resource
sdc      8:32   0   10G  0 disk
└─sdc1   8:33   0   10G  0 part
sr0     11:0    1  628K  0 rom

After encrypting the data disk:
> /dev/sda2: UUID="3c11fba3-32c7-4d0c-b614-aad5630504eb" TYPE="xfs"
> /dev/sda1: UUID="ca02dd2d-a91b-4fb1-b24b-0fb19c18b89d" TYPE="xfs"
> /dev/sdb1: UUID="081659ef-b6f5-419d-b013-f4f6974396e7" TYPE="crypto_LUKS"
> /dev/sdc1: UUID="dc1235bb-65c5-4a13-8a1d-f0e4e15f6aa6" TYPE="crypto_LUKS"
> /dev/sdd1: LABEL="BEK VOLUME" UUID="76BF-9485" TYPE="vfat"
> /dev/mapper/869c7555-41a5-4043-8b7f-ce451290ea7e: UUID="f918fec6-cefd-4abb-8456-374e2f61310f" TYPE="ext4"
> /dev/mapper/04141b05-25f3-46d1-b761-4d8540d11b33: UUID="f32b7279-cc64-466f-b799-fdc3d695dca2" TYPE="ext4"
> NAME                                     MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
> fd0                                        2:0    1    4K  0 disk
> sda                                        8:0    0   32G  0 disk
> ├─sda1                                     8:1    0  500M  0 part  /boot
> └─sda2                                     8:2    0 31.5G  0 part  /
> sdb                                        8:16   0   10G  0 disk
> └─sdb1                                     8:17   0   10G  0 part
>   └─04141b05-25f3-46d1-b761-4d8540d11b33 253:1    0   10G  0 crypt /datadisk1
> sdc                                        8:32   0    7G  0 disk
> └─sdc1                                     8:33   0    7G  0 part
>   └─869c7555-41a5-4043-8b7f-ce451290ea7e 253:0    0    7G  0 crypt /mnt/resource
> sdd                                        8:48   0   48M  0 disk
> └─sdd1                                     8:49   0   47M  0 part
> sr0                                       11:0    1 1024M  0 rom
Basically both /dev/sdb1 <- temporary drive, and /dev/sdc1 <- the data disk, get a new UUID post encryption.

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

ID: 75aaea98-a087-c6d0-61cd-4a2edab37be5
Version Independent ID: 6a2fa1ec-fadc-2d1c-2ab3-8ded33843414
Content: Azure Disk Encryption FAQ
Content Source: articles/security/azure-security-disk-encryption-faq.md
Service: security
GitHub Login: @DevTiw
Microsoft Alias: barclayn

@marinnedea Thanks for your feedback! We will investigate and update as appropriate.

@marinnedea Are you trying to say that the scenario shared by you needs to be added to the FAQ documentation ?

@marinnedea We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

Sorry.. was away last week and had little access to my e-mails.
The current documentation says to make sure you have the /etc/fstab updated with the UUIDs of the data disk partitions before doing the encryption. With the current scenario, this will always lead to a "no boot" situation, because the UUIDs of the data disks will be changed post encryption.
So, you either need to update the documentation to reflect this (I tested and you can encrypt without having the data disks partitions in the /etc/fstab, but you need to manually add them post encryption)  or you need to modify the encryption extension to handle this problem.
If I read correctly the documentation, in case you have data into the data disk and the disk is not added to /etc/fstab before encryption, the encryption will not make a backup of the data before encrypting the disk, therefore I think a fix is needed instead of just updating the documentation.
Please note:  the problem is happening only when using "--encrypt-format-all" parameter. Without it, everything is OK, however, the encryption of a 300GB disk will take ~10 hours, while with the parameter will take  ~1 hour to encrypt the same 300GB disk.
My solution was to have the "nofail" option added to the data disks before encryption and then manually correct the /etc/fstab post encryption.
However, this is an workaround around the problem this scenario poses, not a real solution.


NEXT-14586 Resolve Symfony 5.1 deprecations

1. Why is this change necessary?
Since Symfony 5.1 not setting the framework.router.utf8 option is considered deprecated.

2. What does this change do, exactly?
Set the utf8 option to be true.
3. Describe each step to reproduce the issue or behaviour.
Run tests that interact with the Symfony/Shopware router.
4. Please link to the relevant issues (if any).
https://issues.shopware.com/issues/NEXT-14586
5. Checklist

[ ] I have written tests and verified that they fail without my change => => Not applicable
[x] I have squashed any insignificant commits
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes => Not applicable
[ ] This change has comments for package types, values, functions, and non-obvious lines of code => Not applicable
[x] I have read the contribution requirements and fulfil them.

Not entirely sure why the Cypress step fails, but I can not re-run it either. Could someone from you at Shopware do that for me? I do not think that it is related to my change, but with a re-run we would be certain. Thank you guys!

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-14633
Please use this issue to track the state of your pull request.

Hi @philipgatzka, I have resolved your comments, please have another look.

Thank you for your contribution @TheKeymaster ! 🥳


kafka(ticdc): claim check do not use filepath join to build the full file path.

What problem does this PR solve?

Issue Number: close #10036
What is changed and how it works?
Check List
Tests

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

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`None`

/test dm-integration-test

/retest

/test cdc-integration-storage-test

/retest

/cherry-pick release-7.5


MongoDB tutorial: Update to 3.0 and use proper snippets

Using snippet files like https://github.com/aspnet/AspNetCore.Docs/blob/master/aspnetcore/tutorials/first-mongo-app/samples_snapshot/3.x/SampleApp/Startup.ConfigureServices.AddDbSettings.cs is not allowed. Use the snippet tag
16K PV

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

ID: 5240866d-d0a1-f0dd-7b2c-203e1d69bc4b
Version Independent ID: 83a5cb3b-23bc-4f0c-cd1c-1d1ffeb1131a
Content: Create a web API with ASP.NET Core and MongoDB
Content Source: aspnetcore/tutorials/first-mongo-app.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @prkhandelwal
Microsoft Alias: scaddie

@wadepickett  this is P2 when you've completed all your P0 & P1

Moved to #16196


Server terminated without any warning when memmory usage was high and tenants started login in

Description:
Server terminated without any warning when memory usage was high and tenants started login in
Suggested Labels:
Bug
Suggested Assignees:
N/A
Affected Product Version:
APIM 2.1.0 wum updated
OS, DB, other environment details and versions:
Ubuntu 14.04, MySQL 5.6, IS 5.3.0 as KM
Steps to reproduce:

Create 50 tenants using admin services.
increase the memory usage of the VM to use 99% of the memmory using stress tool [1]

stress --vm-bytes $(awk '/MemFree/{printf "%d\n", $2 * 1.1;}' < /proc/meminfo)k --vm-keep -m 1

using a jmeter script try login into those created tenants.

Observations:
The server had gone down without any warning logs, or head dump.
Related Issues:
N/A
[1] https://linux.die.net/man/1/stress

We didn't encounter this in recent past hence closing the issue. If you encounter the issue in the latest products please reopen the ticket.


Advertise support for Atom in HTTP Accept header

Per https://tools.ietf.org/html/rfc7231#section-5.3.2 HTTP clients may
advertise support for content types via the Accept header.
Some HTTP servers that serve Atom require this, e.g. https://developer.github.com/v3/activity/feeds

This Accept header is too narrow since Elfeed also accepts RSS. A server
that only serves RSS would be right to reject a request from Elfeed with
this header, and that's not what we want. So, at minimum, Elfeed should
specify both.
However, Elfeed already does this: "Accept: /".
Fortunately the GitHub documentation is wrong and that endpoint serves
an Atom feed in response to /, or even with no Accept header at all.
I looked at a few other feed readers, and only found two with precise
Accept headers. Liferea:
Accept: application/atom+xml,application/xml;q=0.9,text/xml;q=0.8,/;q=0.7
QuiteRSS:
Accept: application/atom+xml,application/rss+xml;q=0.9,application/xml;q=0.8,text/xml;q=0.7,/;q=0.6
I'm not thrilled at the idea of using such a complex header, but I
suppose it's technically a little more correct.


SWSD Connector documentation for GA

This is SWSD Connector documentation for GA
should be release - on Feb 12, 2024
Please make sure this documentation will publish when our connector version 1.1.1 will be published also
Thanks

@DougKlopfenstein
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Hi @LiranRomSamanage
Please make the following changes so this pull request can be merged in a timely manner:

Insure that the warnings listed above are fixed. Since all of the warnings are about links to Power BI documentation, just change the beginning of the link from "https://learn.microsoft.com/en-us/power-bi/connect-data..." to "/power-bi/connect-data..." (that is, remove "https://learn.microsoft.com/en-us" from the beginning of the links).
Fix any conflicts between MicrosoftDocs/main and your fork/branch. Some of these conflicts might be caused by the name changes recently made in the overall Microsoft documentation. That is, your article might contain the word "datasets", which is now called "Semantic models". Or it might contain "Azure Active Directory" (or it's abbreviations Azure AD and AAD), which is now called "Microsoft Entra ID".
In the table of contents (toc.yml), remove the "(Beta)" tag from the name of your connector.
In the list of all connectors (connectors/index.md), remove the "(Beta)" tag from the name of your connector.
Since your connector is supported by both Power Query Desktop and Power Query Online, you should add a section about connection to Power Query Online (and differentiate between the section documenting how to connect to Power Query Desktop). For example, see the Azure SQL database connector article for a sample of a connector that is supported in both Power Query Desktop and Power Query Online (as recommended in Example connector articles in the connector certification documentation).

Note also that some of the smaller changes that you've made in this pull request will have to be undone because they do not follow Microsoft style rules (such as using "click" when selecting an item, or removing contractions when Microsoft style rules require contractions to make the docs more informal). The documentation build engine will reject these changes, so they will be undone by our editors before the article is released. Just wanted to let you know so you won't be surprised.

@DougKlopfenstein
I've sync, remove Beta, fix conflicts.

As for the link to "https://learn.microsoft.com/en-us" it is not our content, but link to microsoft how-to guides. we would like our customers will know how to use the features like: incremental-refresh-configure#create-parameters and incremental-refresh-configure#define-policy and incremental-refresh-configure#create-parameters

how would you recommend to add such link?

As for the support Power Cloud and Desktop. we are only Desktop Connector. was and will be on this version. nothing changed.
As for Microsoft style rules - let me know what to change and I will change it.

@Court72  @DougKlopfenstein  -  please review, after my last commit and comment, Thanks

@DougKlopfenstein @Court72  @peter  @Court72 Hey
Any update regarding that? Thx

@DougKlopfenstein @Court72 @peter @Court72 Hey
Any update regarding that? Thx

Hi @LiranRomSamanage
Regarding the http://learn.microsoft.com/en-us links - because the links in your article are actually built into our (Microsoft's) documentation, you don't need the "http://learn.microsoft.com/en-us" portions of the link. In fact, that's why you are getting the error messages. Our build engine is seeing the absolute link you are providing and is requesting that you to remove the "http://learn.microsoft.com/en-us" prefix so that the link becomes a relative link. If you keep the prefix in the article, it will still work, but will only jump to a US English version article. By removing the prefix, the links in your article will then jump to the appropriate article depending on which language the user is currently using.
Regarding being only a Desktop connector - Your connector is also available in Power BI service and Fabric (Dataflow Gen2), both of which are online services. If they are available in online services, you should have a section about how to connect using Power Query Online. However, if you want to get this article out sooner rather than later, that section could be added later after merging what you have already.

@DougKlopfenstein
I don't mind about open the external link on english only.
Is this PR is approve as it is, with warning? and can be merge?

@DougKlopfenstein @peter @Court72
Please approve, the connector is already published and available on desktop.
we need this documentation to be available too
Thanks

@Jak-MS - no one reply or approve this PR. the connector is already live and available, but only the documentation is holding back. Can you please approve so I can merge it?

@LiranRomSamanage - I've made the link corrections as is our policy, but you'll need to commit them.  Unfortunately, I can't merge this without a sign off from @DougKlopfenstein.
@DougKlopfenstein - nudge to take another look, after the link corrections have been committed.  (I'm not sure why I'm unable to commit the changes directly).

@Jak-MS thanks, I removed them.
I still waiting (too long) for approval from @DougKlopfenstein
please assist with this

@LiranRomSamanage
Sorry, but for some reason I was not being notified when you added comments to this pull request.
You don't need me to approve the article - you just need to add a #sign-off comment to this pull request. That should start the process of having our editors look at the article, then merging the article once any editorial changes are made.

#sign-off

#sign-off

#sign-off

Hi @LiranRomSamanage and @giladsmg
The sign-off I did changed the do-not-merge label to ready-to-merge. At this point, our editors will take over to ensure that the article meets minimum spelling, grammar, and Microsoft style rules. Once all of the minimum requirements are met, the changes will be merged.

@LiranRomSamanage @giladsmg - I will merge this now...
I can't edit the files in your branch (this is unusual), but if I could I would make the following changes. They are not critical but are advisable.  You can make them on a follow-up PR.

the Incremental Refresh Setting header should read Incremental Refresh setting .
code blocks and paragraphs that come under a numbered step should be indented 3 spaces
UI text and buttons should be bolded, and our style prefers the word 'select' to 'click'.
(example: 1. Click Done. should be 1. Select **Done**.)
also make sure there are periods at the end of each step. :)

Thanks!


mutex: Revert part of the changes introduced by b88a8cf39ff1019ad787c4316b22ce29c7daa2dc

Summary
Revert part of the changes introduced by b88a8cf39ff1019ad787c4316b22ce29c7daa2dc dues to deadlock in syslog and introduction of cancellation points in kernel for FLAT mode
Impact
Fix syslog
Testing
Pass CI

Let's restore things to a working state and then do a single change for the syslog update.

I was going  to suggest spitting this into 2 PR. A revert and a fix for syslog is that what you are saying?
It appears to me that some of the sweeping changes on master have destabilized the project.  I would revert all the changes on master and work on an upstream branch until the all the issues are addressed and tested. I would also strongly suggest that future changes like these be done on upstream branches and tested before merging.
@pkarashchenko - you are closer to the problem than I am so I leave it up to you make the call on this.

Ok. I will split the change into 2 PRs

@davids5 done. Anyway I was trying to address another part in https://github.com/apache/incubator-nuttx/pull/6376
I think we need to revert libc related changes anyway and then think about better solution.
I found out that currently we have even bigger gap since in case of FLAT build the _SEM_ macro interface is used also for dynamic memory allocation, so malloc and free become cancellation points. I do not have a solid solution for that, but think that we should not rock the boat with changes like https://github.com/apache/incubator-nuttx/pull/6320 introducing even more inconsistency.
IMO we need to revert another part of the changes (that I removed from this PR) and spend some time on a design review so then it will be possible to come up with a solid solution.


Starting with Library on First Tab Crashes the App

Description
Always happens, if I left Documents as the first tab and close the app, it will crash on the next start, all my tabs will be lost. However, if it is not the first tab, the app does not crash and gives "Documents.library-ms" on the title of the tab. Clicking onto the tab can load Documents correctly.
Steps To Reproduce

In Settings -> Preference -> Startup settings, choose Continue where you left off
Open any one of the Libraries from the side panel as the first tab, I used Documents
Close the app through the X on top-right corner
Reopen the app
See the issue

Expected behavior
It should not crash
Files Version
Version: <IP_ADDRESS> OS Version: 10.0.22621.160
Windows Version
Windows 11 Home 22621.160
Relevant Assets/Logs
debug.log
debug_fulltrust.log

@yaichenbaum

Is this still an issue?

@Josh-65 Seems like it's not happening now. Thanks for reminding!


tunnel reports chmod operation not permitted

Version of Warden
0.13.1
Operating System and Installation Method
ubuntu 22
Image
panubo/sshd:1.1.0
warden svc
Describe the Bug

Starting SSHD

Found host keys in keys directory

Fingerprints for dsa host key
1024 MD5:fa:d9:64:2c:6c:19:e1:a3:b5:54:f9:e0:ec:8e:cc:38 root@c398647c1094 (DSA)
1024 SHA256:lSlVNq3uYoQSgBBz9Dlm1Y/WUX9p5Z5Xr7rZIkwzwfc root@c398647c1094 (DSA)
1024 SHA512:39lso0mf6F1cTnbn7YwdS9jPixcu3r/kPstJAxT8VEKKixQwlX5O3Kx54Uh4CZgs3wWVrBEZQZYj6CkEgfEN/A root@c398647c1094 (DSA)
Fingerprints for rsa host key
3072 MD5:91:3e:49:62:f2:7b:d2:b9:db:d1:c7:4a:14:36:6c:85 root@c398647c1094 (RSA)
3072 SHA256:+m+WixpWN0Pf5e3/9hEg5JN0DkBfyriXh04IG907OkQ root@c398647c1094 (RSA)
3072 SHA512:vvQxj46HBKjhHykclgM+0YphxYUwBt3XRxdvQ61kyWoDtgHu3a0cQFw9fq5Z3+fNneNtal4LOMFKaRLJKUEeRg root@c398647c1094 (RSA)
Fingerprints for ecdsa host key
256 MD5:80:4b:07:07:53:0f:30:db:30:0b:a0:9a:25:f2:e1:81 root@c398647c1094 (ECDSA)
256 SHA256:8wCMyi5W+D8WMf8Xxwx483Y0cq2S59l1c5whzc2rBpw root@c398647c1094 (ECDSA)
256 SHA512:X5mf6ZYans1k2T5Z5vnCeXDLvOhg0J24/riBpqiRLMhm4BcYrhjA3pIVe9pGOjWOPCz5In0XK4lMXwaIK38zMw root@c398647c1094 (ECDSA)
Fingerprints for ed25519 host key
256 MD5:69:1c:6c:97:50:ec:2f:40:08:19:a2:52:df:8f:e1:dc root@c398647c1094 (ED25519)
256 SHA256:5IccUhTO2C+prscoNI3Ow55kRhHr5dwPWmNaFAyoZB0 root@c398647c1094 (ED25519)
256 SHA512:NCR+GC6xsyrmEov43Kx88eOWeZcmLyyWtiQuGTu0AwWl5z+VCzaToCD2LV+vQ7iXZAeIuAvWpcd5bpZ2pjiTTg root@c398647c1094 (ED25519)
chmod: /etc/authorized_keys/user: Operation not permitted

To Reproduce

Go to 'warden svc up'

[
Expected Behavior
No response
Additional context
No response

what intrigues me the most is that the panubo image is not in the docker hub images in the official repository

@therocketgroup That would be https://hub.docker.com/r/panubo/sshd

Yes

@navarr very strange because it creates a directory with the same name as the public key making it impossible to connect to the tunnel

Adding user user with uid: 2000, gid: 2000.
2023-04-19 10:24:24 INFO: root account is now locked by default. Set SSH_ENABLE_ROOT to unlock the account.
2023-04-19 10:24:24 INFO: password authentication is disabled by default. Set SSH_ENABLE_PASSWORD_AUTH=true to enable.
2023-04-19 10:24:24 Running /usr/sbin/sshd -D -e -f /etc/ssh/sshd_config
2023-04-19 09:44:50 Server listening on <IP_ADDRESS> port 22.
2023-04-19 09:44:50 Server listening on :: port 22.
2023-04-19 10:05:47 Connection closed by <IP_ADDRESS> port 53272 [preauth]
2023-04-19 10:06:11 User user authorized keys /etc/authorized_keys/user is not a regular file
2023-04-19 10:06:11 User user authorized keys /etc/authorized_keys/user is not a regular file
2023-04-19 10:06:11 Connection closed by authenticating user user <IP_ADDRESS> port 49326 [preauth]
2023-04-19 10:22:34 User user authorized keys /etc/authorized_keys/user is not a regular file
2023-04-19 10:22:34 User user authorized keys /etc/authorized_keys/user is not a regular file
2023-04-19 10:22:34 Connection closed by authenticating user user <IP_ADDRESS> port 59746 [preauth]
2023-04-19 10:23:11 User user authorized keys /etc/authorized_keys/user is not a regular file
2023-04-19 10:23:11 User user authorized keys /etc/authorized_keys/user is not a regular file
2023-04-19 10:23:11 Connection closed by authenticating user user <IP_ADDRESS> port 33290 [preauth]
2023-04-19 10:24:10 Received signal 15; terminating.
2023-04-19 10:24:24 Server listening on <IP_ADDRESS> port 22.
2023-04-19 10:24:24 Server listening on :: port 22.
2023-04-19 10:24:27 kex_exchange_identification: client sent invalid protocol identifier "GET / HTTP/1.1"
2023-04-19 10:24:28 kex_exchange_identification: client sent invalid protocol identifier "GET / HTTP/1.1"
2023-04-19 10:24:32 kex_exchange_identification: client sent invalid protocol identifier "GET / HTTP/1.1"
2023-04-19 10:24:37 kex_exchange_identification: client sent invalid protocol identifier "GET / HTTP/1.1"
2023-04-19 10:25:08 kex_exchange_identification: client sent invalid protocol identifier "GET / HTTP/1.1"

I'm going through the same problem here. Any solutions or suspicions about it?
tunnel  | > Starting SSHD
tunnel  | >> Found host keys in keys directory
tunnel  | >>> Fingerprints for rsa host key
tunnel  | 3072 MD5:b8:7f:3a:bf:7f:bd:ba:04:10:7d:9b:55:8b:75:15:59 root@f4902c000f6e (RSA)
tunnel  | 3072 SHA256:FnMA9o+qol6lokoyB6QlSM+3OYhbEUXtf1TcK5GL5i4 root@f4902c000f6e (RSA)
tunnel  | 3072 SHA512:3Xamu8iN6cfBRoSr1FifXINsU2zl9qmvLFHAggQnO3AydHiUnq2Myz4Zrkhz2xkjStilbB3jcav/XWavqj346g root@f4902c000f6e (RSA)
tunnel  | >>> Fingerprints for ecdsa host key
tunnel  | 256 MD5:7d:19:0a:39:1f:8f:89:d9:8a:8e:2d:49:1f:0a:d5:49 root@f4902c000f6e (ECDSA)
tunnel  | 256 SHA256:Ri573nieCoiA+dexXq+jXvuGCX9KE3N3d9XX30Qndtc root@f4902c000f6e (ECDSA)
tunnel  | 256 SHA512:3Via2+Xan/tOFDWtaLMfDfPd0cs6pik2CxdFw0TubOQ011r7gOrMHPcHg0ZRyShUCKayUShNPqEAU2L91truaw root@f4902c000f6e (ECDSA)
tunnel  | >>> Fingerprints for ed25519 host key
tunnel  | 256 MD5:5b:47:2d:34:e6:54:b3:1b:ed:fa:56:cf:fc:a3:da:50 root@f4902c000f6e (ED25519)
tunnel  | 256 SHA256:1/uC4NDsJfHhFX386Mvgx6pHOQhyHICiAYxvmJbSKaA root@f4902c000f6e (ED25519)
tunnel  | 256 SHA512:lXberaxcJulDBbrHwQMjVqv+UrhaVa4yP38sbRZzznuF1CnS5hyrQtCV5OO2ABvdJFeGPtLCjGWQR35oK/1tSw root@f4902c000f6e (ED25519)
tunnel  | chmod: /etc/authorized_keys/user: Permission denied


Create Non-Mod version of the PlayerDataTracker

PlayerDataTracker is great and will continue it's life for modded runs, however, if someone wanted to use it in a non-modded run, it won't work.  Need to write a stand-alone app that can read from the save file and work the same way as PlayerDataTracker without modding the game.

There is very little reason why you can't install the API and just the PlayerDataTracker mod.

I really don't work on modding HK anymore, but the notion here was to allow for tracking stuff without mods.  IE tracking stuff during a speedrun where mods are banned.  In any case, since I'm not really active anymore it's a moot point unless someone else takes up this project.


Filter realtime results

Is it possible to observe collection with attached query? For example I want to be notified only about changes in records belonging to a specific user.

Realtime events supports filtering only via the collection API rules that are defined by the admins.
When you subscribe to an entire collection, eg. projects, the collection's ListRule will be used to determine whether the subscriber has access to receive the event message.
When you subscribe to a single record, eg. projects/RECORD_ID, the collection's ViewRule will be used to determine whether the subscriber has access to receive the event message.
Admin accounts receive all events (API rules don't apply to them).
There is no client-side filter like query support for the event data. I may consider it in the future, but for now you can filter manually the received event in the callback function by using the record property of the event data, eg.:
client.realtime.subscribe('projects', function (e) {
    if (e.record.status === 'active') {
        // do something with the record...
        console.log(e.record.title);
    }
});

I'll move the issue to Q&A discussion.


hcloud: 1.5.0 -> 1.6.0

Motivation for this change
update hcloud: 1.5.0 -> 1.6.0
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build hcloud

Success on x86_64-linux (full log)
Attempted: hcloud
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/bz4pjavzr0z9l23dpy4cfv8rxd0rl4xz-hcloud-1.6.0-bin
shrinking /nix/store/bz4pjavzr0z9l23dpy4cfv8rxd0rl4xz-hcloud-1.6.0-bin/bin/hcloud
strip is /nix/store/gpc2wld1s0c6qzx9326cwn1wcx29xzsj-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/bz4pjavzr0z9l23dpy4cfv8rxd0rl4xz-hcloud-1.6.0-bin/bin
patching script interpreter paths in /nix/store/bz4pjavzr0z9l23dpy4cfv8rxd0rl4xz-hcloud-1.6.0-bin
checking for references to /build in /nix/store/bz4pjavzr0z9l23dpy4cfv8rxd0rl4xz-hcloud-1.6.0-bin...
strip is /nix/store/gpc2wld1s0c6qzx9326cwn1wcx29xzsj-binutils-2.30/bin/strip
/nix/store/bz4pjavzr0z9l23dpy4cfv8rxd0rl4xz-hcloud-1.6.0-bin

Success on aarch64-linux (full log)
Attempted: hcloud
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/dg7f4hbigqx909kkw47qv9bn6lps1yfc-hcloud-1.6.0-bin
shrinking /nix/store/dg7f4hbigqx909kkw47qv9bn6lps1yfc-hcloud-1.6.0-bin/bin/hcloud
strip is /nix/store/ah0va6j4cnwj9nx4j6rwcfc8nh785jwm-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/dg7f4hbigqx909kkw47qv9bn6lps1yfc-hcloud-1.6.0-bin/bin
patching script interpreter paths in /nix/store/dg7f4hbigqx909kkw47qv9bn6lps1yfc-hcloud-1.6.0-bin
checking for references to /build in /nix/store/dg7f4hbigqx909kkw47qv9bn6lps1yfc-hcloud-1.6.0-bin...
strip is /nix/store/ah0va6j4cnwj9nx4j6rwcfc8nh785jwm-binutils-2.30/bin/strip
/nix/store/dg7f4hbigqx909kkw47qv9bn6lps1yfc-hcloud-1.6.0-bin

Success on x86_64-darwin (full log)
Attempted: hcloud
Partial log (click to expand)
find: '/nix/store/axn8pkn0wnagcp21ill37i2fp00yn2jr-hcloud-1.6.0': No such file or directory
find: '/nix/store/axn8pkn0wnagcp21ill37i2fp00yn2jr-hcloud-1.6.0': No such file or directory
find: '/nix/store/axn8pkn0wnagcp21ill37i2fp00yn2jr-hcloud-1.6.0': No such file or directory
find: '/nix/store/axn8pkn0wnagcp21ill37i2fp00yn2jr-hcloud-1.6.0': No such file or directory
find: '/nix/store/axn8pkn0wnagcp21ill37i2fp00yn2jr-hcloud-1.6.0': No such file or directory
find: '/nix/store/axn8pkn0wnagcp21ill37i2fp00yn2jr-hcloud-1.6.0': No such file or directory
find: '/nix/store/axn8pkn0wnagcp21ill37i2fp00yn2jr-hcloud-1.6.0': No such file or directory
find: '/nix/store/axn8pkn0wnagcp21ill37i2fp00yn2jr-hcloud-1.6.0': No such file or directory
find: '/nix/store/axn8pkn0wnagcp21ill37i2fp00yn2jr-hcloud-1.6.0': No such file or directory
/nix/store/1lkan9ycj6y25j9kafmyrkbsdmph76r1-hcloud-1.6.0-bin

Typo in commit message fixed during merge.

Ah, sorry; thanks for fixing and merging!


[QST] Triton MLIR

@srush
Always appreciate your wonderful OSS educational contributions!
I'm relatively familiar with CUDA and triton but less so with machine learning compilers and am interested in getting into the weeds of triton's compilation pipeline.
I've come across a few resources for learning MLIR as well as related projects such as TVM (which has a comprehensive set of tutorials / learning materials spearheaded by Tianqi Chen of CMU), but have yet to bridge the gap from basic MLIR to something on the scale of triton.
The overarching motivation -- other than the fact that ML compilers are super-interesting :) -- is that in a world of increased demand for ML training / inference but limited GPU (NVIDIA) supply, the ability to write code that is backend-agnostic is evermore important.
A few questions:

Are you aware of any resources for learning MLIR incrementally, ideally building from basics to something like a toy triton, and more ambitiously, understanding enough of the triton backend to be able to contribute new optimization passes?
Is this something you're interested in and possibly collaborating on?

I'd be willing to do as much of the heavy lifting as needed:

I'd envision a step by step walkthrough of each of triton tutorials, starting with vec-add.
The goal would be to understand how each pass of the compilation pipeline translates high-level python to performant device code.
Something that pulls apart each component of the C++ MLIR pipeline and provides greater visibility -- and hackability -- than simply observing the output of MLIR_ENABLE_DUMP.

cc @Jokeren

Hi Jerome,
Nice to hear from you. This seems like a very interesting project. It is a bit beyond my area of expertise as I have only dabbled a bit in the internals of MLIR generation and lowering. My only worry is that this area does seem like it is evolving quite quickly so there may not yet be stable enough foundations to document for lay-users.
@Jokeren might have more to add.

I doubt the Triton developers will find the time to craft documentation or develop tutorials.
 Honestly, their enthusiasm has taken me by surprise... I've glanced over a few of these blogs and, honestly, they're top-notch.

@Jokeren: Which blogs are you referring to?  I'd certainly be interested in taking a gander!
@srush: no worries -- let me see how far I can take this on my own and will be happy to share any progress.

Wait, do you read Chinese? I meant they are written in Chinese, or you plan to translate?

Plan to translate -- wonders of multilingual llms (or google translate for that matter).  I am also Chinese.

That's great. Feel free to search with keyword "triton" on zhihu.com :)
That's what I'm referring to

@Jokeren
Thanks -- yes, I've come across many of those already.  Many deep dives into all things CUDA / Cutlass there as well, haha.
Are you planning on teaching a course on MLIR / deep learning compilers at your university?

Are you planning on teaching a course on MLIR / deep learning compilers at your university?

Maybe not. They didn't assign me to a compiler course unfortunately.


Cannot Infer Types if Type Signatures Left Out

I know that Haskell idiomatically uses type signatures to provide commenting, but Haskell cannot infer types on the UI builder etc if type signatures are left out.
Same applies to Widgets.
I think that for at least demonstrating monomer, it's useful to include the version without the type signatures because the type signature is liable to confuse newbies to Haskell.
Not sure if there's a practical workaround, though.

@liamzee I'm not sure to which specific example you refer.
Sometimes leaving out the signature is clearer, but getting weird compilation errors can be even more confusing for new users. Given that Monomer relies quite a bit on lenses and that its compilation errors can be quite scary, having an explicit type signature reduces this type of problem.

I've been trying to build a minimal monomer application, i.e, everything is left out, all you have is a window, for the minimal amount of code to get monomer to compile and open a window.
If you use void types for model and events, you'll need type signatures, and even if you populate the events, I think type inference will still fail without an explicit type signature.
Not really that big a deal; the workarounds are good enough, and I don't think monomer currently attracts anyone who might be interested in a completely simplified and unidiomatic type sig-less model.

Closed. This is extremely niche, but in fact, it's possible to completely avoid data declarations entirely simply by reusing () as both a model and event type.
So the minimal app for demonstration only can actually be much, much shorter.


Type checking errors after installing @types/styled-components

I'm having these weird errors after I install @types/styled-components

I have pushed the code to this branch: https://github.com/alveshelio/razzle-typescript-redux-styled-components-starter-kit/tree/styled-components
I don't understand why @types/styled-components is throwing these errors at all.

I've just noticed something, when I install @types/styled-components, it installs two packages in types, styled-components and react-native. If I manually delete the react-native folder I don't get these errors.
I've deleted folder node_modules and reinstalled but it comes back :(


CI: K8sPolicyTest varied flakes

This seems like a race between adding this policy and regenerating. My current guess is that the way we wait for k8s netpols to regenerate is not as robust as what we do for CNPs.
These are all of the form:
Expected command: kubectl exec -n<PHONE_NUMBER>21k8spolicytestbasictestchecksallkindofkubernetespoli app2-64975875bc-j29hw -- curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 8 http://<IP_ADDRESS>/ -w "time-> DNS: '%{time_namelookup}(%{remote_ip})', Connect: '%{time_connect}',Transfer '%{time_starttransfer}', total '%{time_total}'"
To have failed, but it was successful:

https://jenkins.cilium.io/job/Ginkgo-CI-Tests-Pipeline/10979/testReport/junit/Suite-k8s-1/11/K8sPolicyTest_Basic_Test_Denies_traffic_with_k8s_default_deny_ingress_egress_policy/
https://jenkins.cilium.io/job/Ginkgo-CI-Tests-Pipeline/10976/testReport/junit/Suite-k8s-1/18/K8sPolicyTest_Basic_Test_Denies_traffic_with_k8s_default_deny_egress_policy/
https://jenkins.cilium.io/job/Ginkgo-CI-Tests-Pipeline/10970/
https://jenkins.cilium.io/job/Ginkgo-CI-Tests-Pipeline/10967/
There may be cross-test effects. In one case a number of tests failed later with cilium preflight failures (no socket found) https://jenkins.cilium.io/job/Ginkgo-CI-Tests-Pipeline/10971/

From weekly meeting: Maybe related to CEP status changes?


Fix 314

Codecov Report

Merging #315 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #315      +/-   ##
==========================================
+ Coverage   63.75%   63.77%   +0.02%
==========================================
  Files          72       72
  Lines        4218     4171      -47
==========================================
- Hits         2689     2660      -29
+ Misses       1529     1511      -18

Impacted Files
Coverage Δ

...tural_language_inference/decomposable_attention.py
96.55% <100%> (+13.72%)
:arrow_up:

jack/tfutil/activations.py
0% <0%> (-60%)
:arrow_down:

Continue to review full report at Codecov.

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