Add ability to auto-recover from a failing collector

See https://github.com/snowplow/snowplow-python-tracker/issues/151

The functionality is not immediately sticking out to me in the Python tracker, but as I looked further into the way the dotnet-tracker is built, it I think the functionality may already be accessible through the existing Emitter class:
https://github.com/snowplow/snowplow-dotnet-tracker/blob/b7942a9acc98cd75ea9127fdfb6695e955135e87/Snowplow.Tracker/Emitters/Emitter.cs#L146
Since the event that is returned to onFailure contains the original payload that was added to the buffer, by simply reinserting the event into the buffer the same objective can be achieved.
foreach (Dictionary<string,string> eventPayload in unsentEvents) {
     e.Input(eventPayload)
};

//manually flush
  t.Flush(false);

Please note that if the event fails again, it will be duplicated in the onFailure list created earlier.  Maybe some sort of de-duping in the list before flushing? We could also encounter an infinite loop if the HttpResonse is never "OK".
I am happy to work on implementing this functionality, however, I think it needs some additional planning.

It could be helpful to understand how the mobile trackers achieve this - @jbeemster?

The mobile trackers have a persistent SQLite database storing all of the events.  So they are simply never removed from the database until they are successfully sent.
Perhaps we need a better queue than the buffer to store and remove events from and to only remove them from said queue on successfully sending them?  It seems easier than constantly re-adding failed events to the buffer.

Thanks Josh - @digitaltouch / @fblundun, what would be a sensible equivalent of SQLite for a .NET tracker?

MSMQ will probably be the easiest to extend.  There is already a MSMQ emitter implemented... Working to better understand the "Offline" logic built into the tracker already.  May be easiest to keep everything implemented as is, just add any events without an "OK" response to the Queue, not just unavailable events:
https://github.com/snowplow/snowplow-dotnet-tracker/blob/master/Snowplow.Tracker/Emitters/Emitter.cs#L239
Thoughts @fblundun?

I've added some documentation on the simplest way to achieve this with the Python Tracker here. It works in a similar manner to @digitaltouch's original suggestion, feeding failed events back into the emitter's input function.
You are right that this approach would be problematic in the this Tracker if offline mode is enabled - every failed event would both be fed back in to the original emitter and sent to the "backup emitter".
The way the backup emitter currently works, if sending an event throws a WebException the event is stored in an MSMQ queue. Whenever there is a network availability change event, we attempt to resend those failed events.
Sending all events without an OK response to the queue, rather than just those which throw a WebException, sounds good to me!

Thanks @fblundun . Sending all events without an OK response to the queue sounds like the way to go!

Making progress -
https://github.com/digitaltouch/snowplow-dotnet-tracker/blob/master/Snowplow.Tracker/Emitters/Emitter.cs#L215-L242
All that was added was offlineHandle(payload) and offlineHandle(data)
I received a strange error when the MSMQ got 15 records or more:
"system.invalidoperationexception collection was modified enumeration may not execute" and it was pointing to: https://github.com/digitaltouch/snowplow-dotnet-tracker/blob/master/Snowplow.Tracker/Emitters/Emitter.cs#L170
Did you see anything like this when writing the tracker?
Just ran around 1,000,000 records through with around 1,000 unsuccessful being added to the MSMQ and successfully flushing.

That's interesting... The fact that this happens intermittently suggests a concurrency bug. It could caused by the absence of a lock on the tasks list - perhaps these two lines are being executed concurrently?
My hypothesis is that the exception occurs when one thread is inserting into the tasks list with while another thread is calling .toList() on it.

Does it still happen if you do something like this?
    private readonly object Locker = new object();

    protected override void Flush(bool sync, bool forced)
    {
        lock(Locker)
        {
            Task flushingTask = Task.Factory.StartNew(() =>
            {
                if (forced || this.buffer.Count >= this.bufferSize)
                {
                    SendRequests();
                }
            });
            tasks.Add(flushingTask);
            tasks = tasks.Where(t => !t.IsCompleted).ToList();

            if (sync)
            {
                Log.Logger.Info("Starting synchronous flush");
                Task.WaitAll(tasks.ToArray(), 10000);
            }
            else
            {
                Thread.Yield();
            }
        }
    }

To answer your original question, I don't remember ever seeing this exception when I was originally developing the Tracker. Perhaps I wasn't using high enough event volumes for it to become apparent.

Great catch... I was scratching my head on this most of the day yesterday.
It has run successfully for an hour so far with the lock on the tasks list.  I will monitor of the next couple of days and then issue the Pull Request if everything appears to be working.

Glad to hear it! Let us know if anything else goes wrong...

Not sure why Ed closed this, it will close on merge to master


Python: Fix Reads + Misc Fixes

This PR fixes the following:

When handing a buffer of bytes from C++ to Python, the usage of
c_char_p instead of c_void_p resulted in the buffer being treated as a
null-terminated string, resulting in the clipping of the data anytime
zero was encountered. This resulted in reads not quite working.

Fixed up the logic that automatically looked up the right type of
cluster object when processing a read response.

Simplified the API for WriteAttribute by converting the generated
classes for attributes into dataclasses with a 'value' member in them.

Added Python docstrings for read and write APIs

fast  track: python only changes made by a domain owner.


Remove cert manager subscription check

@mandymchu
Would you please review it again? We keep SKIP_INSTALL unchanged for cert-manager-webhook checking

lgtm
test passed for cert manager only, but the script at this moment failed to install licensing due to the package manifest name mismatched

Thank you @mandymchu
We will handle the licensing package name issue in a separate PR


[question] Unable to update zwave-js config on Docker

I see there is a new config version of zwave-js but i'm not able to update it, this is the error message :
17:15:18.466 DRIVER Config update failed: Package manager exited with code 1 Error updating root package.json: This directory tree does not contain a direc tory with package.json and a lockfile!

I have the same issue on HA Supervised.

Same story. Perhaps this is because current directory is .../bin.

Same Error on my Installation. Docker with using a local folder on a RPI4

If using volumes I saw this note was added to the readme file:
If you want to support devices config updates you also need to setup a volume on /usr/src/app/node_modules/@zwave-js/config:
docker run --rm -it -p 8091:8091 -p 3000:3000 --device=/dev/ttyACM0 --mount source=zwave-config,target=/usr/src/app/node_modules/@zwav
I'm not using volumes and use a local folder to store data, and the config updated fine with no errors for me:
2021-05-02 15:22:07.856 INFO ZWAVE: Calling api installConfigUpdate with args: [ [length]: 0 ]
2021-05-02 15:22:08.471 INFO ZWAVE: Success zwave api call installConfigUpdate { success: true, message: 'Success zwave api call', result: false }

The only volume defined by K8S@home chart is /usr/src/app/store, which makes total sense.
Making .../node_modules user-controlled sounds unwise.
Since the chart uses the "legitimate" container image, the issue is perhaps either in the Dockerfile (not the relevant config is pulled), or in the build process (obsolete layer persists), or in the whole bundle behaviour, attempting to alter supposedly read-only files.

I run z2m in Docker, and was having the same experience as @mwav3: I received the same success messages when running the update (no errors), but the config update bubble did not go away.
I was able to manually update the config by connecting to a shell inside the Docker container (in my case, docker-compose exec zwave2mqtt /bin/sh). Once I was inside the container, I ran npm update @zwave-js/config which updated a bunch of packages.
After that update finished, I re-ran the config update from within the z2m web UI. The log output was the same, but the 2nd log message took a long time to come through (≈40s), and the update bubble went away. See timestamps:
2021-05-02 22:53:42.994 INFO ZWAVE: Calling api installConfigUpdate with args: [ [length]: 0 ]
2021-05-02 22:54:22.354 INFO ZWAVE: Success zwave api call installConfigUpdate { success: true, message: 'Success zwave api call', result: true }

The update bubble is still gone after a z2m reboot and a config update check.
This is certainly not a fix, but it is a workaround in case someone needs an updated config (or just wants the bubble to go away).

Thanks this command worked.  I did get some warnings when running npm update @zwave-js/config
/usr/src/app # npm update @zwave-js/config
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated<EMAIL_ADDRESS>babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.

added 676 packages, changed 2 packages, and audited 2266 packages in 43s

186 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
npm notice
npm notice New minor version of npm available! 7.6.0 -> 7.11.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v7.11.2
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
/usr/src/app #

Also took a few minutes to update but it worked and the bubble is gone
2021-05-02 19:42:54.989 INFO ZWAVE: Calling api installConfigUpdate with args: [ [length]: 0 ]
2021-05-02 19:46:00.574 INFO ZWAVE: Success zwave api call installConfigUpdate { success: true, message: 'Success zwave api call', result: true }

I was about to post this as a bug and found this issue.
I can confirm that the above command does indeed cause the update notification to go away.
But I'm not sure what was supposed to be updated.
the notification said that "zwave-js 7.3.1-some_date_value" was available. After running the above command, then restarting the container, then clicking the update from within the notification box and waiting for the notification to clear I still have zwave-js version 7.3.0.
Is that expected or should have the zwave-js version been updated?
This is the first time I've ever noticed that notification icon in the top corner or at least the first time I've actually seen an active notification.

@finity69x2 this is updating the z-wave js config package, which is published separately. Being published separately means (ostensibly) people can pull down updates to device configuration without having to update the entire z-wave js core package.
7.3.1-20210502 was current until about 25 minutes ago, when 7.3.1-20210503 was published. Interestingly enough, I did not have a problem updating to that version using the standard z2m UI.

The problem is that the config update tries to bump the config version by loocking for package-lock.json but ATM I'm deleting it in Dockerfile here. @airdrummingfool the second time you tried to run the update it worked because after you manually installed it the package-lock.json has been recreated


Remove reference and use of dataStream everywhere in tests

Background:
I believe existing ProtocolsConfigure needlessly passes an empty data stream to processMessage, it is unnecessary because we made a decision (#139) to have the protocol definition defined in the descriptor.
Task Details:

Remove reference and use of dataStream everywhere in tests

Picking Up This Issue:

If you'd like to work on this, please comment "picking this up" below, and I'll assign the issue to you

Questions:

If you need assistance or clarification, feel free to comment below.
Feeling overwhelmed? Join our #hack-together channel and collaborate with a buddy.
New to open-source? Check out our Hacktober #getting-started channel.
Leaderboard: Check your ranking after finishing this task.

Resources:

Creating a Pull Request: If you're new to GitHub and unsure how to create a pull request, follow this step-by-step guide.

Remember, communication is key! If you have any questions or face any challenges, we're here to help so please don't hesitate to reach out.
Good Luck! 🍁

Picking this up


GVRAnimation::new GVRAnimation - nested animation crashes api

When trying to nest animations the api crashes.
@Override
public void onStep() {
(...)
     new GVROpacityAnimation(spaceSceneObject, 1f, 0f).setOnFinish(new GVROnFinish() {
            @Override
            public void finished(GVRAnimation animation) {
                new GVROpacityAnimation(shipSceneObject, 2.45f, 1f).setOnFinish(new GVROnFinish() {
                    @Override
                    public void finished(GVRAnimation animation) {

                    }
                }).start(mGVRContext.getAnimationEngine());
            }
        }).start(mGVRContext.getAnimationEngine());
    }
(...)
}

Nathan, I can not reproduce this issue on 1.6.5, whether I launch the nested animation from onInit() or onStep(). Even when I do something really dumb - launching the nested animation on every onStep(), so that there are hundred of animations running, stepping on each other - I can not make it crash.
I don't think there's any way to attach a tarball to this issue; could you please mail me the full source of the app that's crashing for you?

Hi Jon,
we were using an older version of gvrf when we reported this issue. We updated it and it's now working just as you said.
I'm closing this issue.


Update SDL2 package to remove separate SDL2-static target

see https://github.com/hunter-packages/SDL2/commit/8926da202eb67c85fd4acc8ecd6438469df20e16

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.2001
https://travis-ci.org/ingenue/hunter/builds/256646633?utm_source=github_status&utm_medium=notification

Something wrong with CMake code:
CMake Error at /home/travis/build/ingenue/hunter/_testing/Hunter/_Base/bfe716a/7c86f54/266cf4a/Build/SDL2/Build/SDL2-Release-prefix/src/SDL2-Release-stamp/SDL2-Release-install-.cmake:16 (message):
  Command failed: 1

   '/home/travis/build/ingenue/hunter/_ci/cmake/bin/cmake' '-Dmake=' '-Dconfig=' '-P' '/home/travis/build/ingenue/hunter/_testing/Hunter/_Base/bfe716a/7c86f54/266cf4a/Build/SDL2/Build/SDL2-Release-prefix/src/SDL2-Release-stamp/SDL2-Release-install--impl.cmake'

  See also

    /home/travis/build/ingenue/hunter/_testing/Hunter/_Base/bfe716a/7c86f54/266cf4a/Build/SDL2/Build/SDL2-Release-prefix/src/SDL2-Release-stamp/SDL2-Release-install-*.log

make[2]: *** [SDL2-Release-prefix/src/SDL2-Release-stamp/SDL2-Release-install] Error 1
make[1]: *** [CMakeFiles/SDL2-Release.dir/all] Error 2
make: *** [all] Error 2

should be working now

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.2003
https://travis-ci.org/ingenue/hunter/builds/256690855?utm_source=github_status&utm_medium=notification

All toolchains except vs-14-2015 failed on Windows.

Guess which toolchain I tested with locally? :P
will fix
On Jul 23, 2017 11:06 PM, "Ruslan Baratov"<EMAIL_ADDRESS>wrote:

All toolchains except vs-14-2015 failed on Windows.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ruslo/hunter/pull/896#issuecomment-317285657, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABCumrlNgEE89M7RgPZJPhAcKhfZa_oiks5sQ8PVgaJpZM4OghW2
.

Ok, should work now

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.2008
https://travis-ci.org/ingenue/hunter/builds/256860415?utm_source=github_status&utm_medium=notification

Uploading:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.2014
https://travis-ci.org/ingenue/hunter/builds/256914867?utm_source=github_status&utm_medium=notification

Released: https://github.com/ruslo/hunter/releases/tag/v0.19.39


move files, env-defs into datmo_file, datmo_environment folder during datmo snapshot checkout

[x] Create a file hash for contents in datmo_files before checkout and compare with respective file hash for that snapshot
[x] Create a file hash for contents in datmo_environment before checkout and compare with respective file hash for that snapshot

finished in PR #163


limitation of loop by number?

for(let i=0;i<100000;i++){
	console.log("a");
}

Result of above code is
node b.js|wc
  100000  100000  200000

But in the case of nectar
 ./b |wc
   83328   83328  166656

on Mac OS 10.14.6.
Something is wrong about how to deal with loop's number, I think.

hi @hikarine3 , thank you for the bug reporting,
It's a problem with String management, I will solve it,
Try this code :
for(let i=0;i<100000;i++){
	console.log(1);
}

Result:
loop.exe |wc
 100000  100000  200000

It should be corrected, can you try again ?
For benchmark or speed purpose, you can use the --preset speed flag

same code
for(let i=0;i<100000;i++){
	console.log("a");
}

but I encountered error this time.
nectar  --version
NectarJS v0.5.27

nectar b.js
[*] Generating source file
[*] Compiling

time deno ./b|wc
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Utf8Error { valid_up_to: 0, error_len: Some(1) }', cli/compilers/js.rs:15:13
stack backtrace:
   0: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
   1: core::fmt::write
   2: std::io::Write::write_fmt
   3: std::panicking::default_hook::{{closure}}
   4: std::panicking::default_hook
   5: std::panicking::rust_panic_with_hook
   6: rust_begin_unwind
   7: core::panicking::panic_fmt
   8: core::result::unwrap_failed
   9: std::future::poll_with_tls_context
  10: std::future::poll_with_tls_context
  11: <std::future::GenFuture<T> as core::future::future::Future>::poll
  12: <core::pin::Pin<P> as core::future::future::Future>::poll
  13: futures_util::stream::try_stream::TryStreamExt::try_poll_next_unpin
  14: <deno_core::modules::RecursiveModuleLoad as futures_core::stream::Stream>::poll_next
  15: <deno_core::modules::RecursiveModuleLoad as futures_core::stream::Stream>::poll_next
  16: std::future::poll_with_tls_context
  17: <std::future::GenFuture<T> as core::future::future::Future>::poll
  18: <std::future::GenFuture<T> as core::future::future::Future>::poll
  19: std::thread::local::LocalKey<T>::with
  20: tokio::macros::scoped_tls::ScopedKey<T>::set
  21: tokio::runtime::basic_scheduler::BasicScheduler<P>::block_on
  22: tokio::runtime::context::enter
  23: deno::tokio_util::run_basic
  24: deno::main
  25: std::rt::lang_start::{{closure}}
  26: std::panicking::try::do_call
  27: __rust_maybe_catch_panic
  28: std::rt::lang_start_internal
  29: main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
       0       0       0

In the case of
nectar  --version
NectarJS v0.5.27

result is same
time ./b|wc
   83325   83325  166650

but is it correct version which I should retry?

Sorry i only pushed the code on github, i will publish the update on npm soon

The update is published on NPM, could you try again ?

As result, it is resolved, thanks!
In terms of the speed, speed is almost same with node.js with --preset speed flag.
########
time node b.js|wc
100000  100000  200000
real	0m0.737s
user	0m0.757s
sys	0m0.379s
########
time deno b.js|wc
100000  100000  200000
real	0m0.348s
user	0m0.221s
sys	0m0.255s
########
nectar --preset speed b.js;
time ./b|wc
real	0m0.747s
user	0m0.620s
sys	0m0.384s

Oh, but in the following case, the result is still but as output.
for(let i=0;i<100000;i++){
	for(let y=0;y<10;y++){
		console.log("a");
	}
}

HajimenoMacBook-ea:tmp hajimekurita$ time node c.js|wc
1000000 1000000 2000000
real	0m4.815s
user	0m4.803s
sys	0m3.216s
HajimenoMacBook-ea:tmp hajimekurita$ time deno c.js|wc
1000000 1000000 2000000
real	0m2.582s
user	0m1.540s
sys	0m2.370s
HajimenoMacBook-ea:tmp hajimekurita$ nectar --preset speed c.js;time ./c|wc
[] Generating source file
[] Compiling
10      10      20
real	0m0.009s
user	0m0.006s
sys	0m0.005s

It's the body parser of the loop, i will correct it

commit 7242a5c should correct it

Error happened when compiling
console.log("B");

nectar --version; nectar  a.js;time ./a|wc
NectarJS v0.5.31
[*] Generating source file
[*] Compiling
In file included from /Users/hajimekurita/tmp/.nectar/ssfna/a.cpp:42:
/Users/hajimekurita/tmp/.nectar/ssfna/njs.h:788:62: error: no matching constructor for initialization of '__NJS_Class_String'
                REGISTER[_array.get().a->__NJS_VALUE[_index]._ptr].s = new __NJS_Class_String(REGISTER[_value._ptr].s->__NJS_VALUE.c_str());
                                                                           ^                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/hajimekurita/tmp/.nectar/ssfna/njs.h:73:7: note: candidate constructor (the implicit copy constructor) not viable: no known conversion from 'const std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::value_type *' (aka 'const char *') to 'const __NJS_Class_String' for 1st argument
class __NJS_Class_String : public __NJS_Class_Object
      ^
/Users/hajimekurita/tmp/.nectar/ssfna/njs.h:73:7: note: candidate constructor (the implicit move constructor) not viable: no known conversion from 'const std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::value_type *' (aka 'const char *') to '__NJS_Class_String' for 1st argument
class __NJS_Class_String : public __NJS_Class_Object
      ^
/Users/hajimekurita/tmp/.nectar/ssfna/njs.h:77:5: note: candidate constructor not viable: 1st argument ('const std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::value_type *' (aka 'const char *')) would lose const qualifier
    __NJS_Class_String(char* _str);
    ^
1 error generated.
[!] Compilation error
Error: Command failed: g++ -std=c++11 /Users/hajimekurita/tmp/.nectar/ssfna/a.cpp -O1 -fpermissive -w -s   -o /Users/hajimekurita/tmp/a
In file included from /Users/hajimekurita/tmp/.nectar/ssfna/a.cpp:42:
/Users/hajimekurita/tmp/.nectar/ssfna/njs.h:788:62: error: no matching constructor for initialization of '__NJS_Class_String'
                REGISTER[_array.get().a->__NJS_VALUE[_index]._ptr].s = new __NJS_Class_String(REGISTER[_value._ptr].s->__NJS_VALUE.c_str());
                                                                           ^                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/hajimekurita/tmp/.nectar/ssfna/njs.h:73:7: note: candidate constructor (the implicit copy constructor) not viable: no known conversion from 'const std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::value_type *' (aka 'const char *') to 'const __NJS_Class_String' for 1st argument
class __NJS_Class_String : public __NJS_Class_Object
      ^
/Users/hajimekurita/tmp/.nectar/ssfna/njs.h:73:7: note: candidate constructor (the implicit move constructor) not viable: no known conversion from 'const std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::value_type *' (aka 'const char *') to '__NJS_Class_String' for 1st argument
class __NJS_Class_String : public __NJS_Class_Object
      ^
/Users/hajimekurita/tmp/.nectar/ssfna/njs.h:77:5: note: candidate constructor not viable: 1st argument ('const std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::value_type *' (aka 'const char *')) would lose const qualifier
    __NJS_Class_String(char* _str);
    ^
1 error generated.

    at checkExecSyncError (child_process.js:616:11)
    at execSync (child_process.js:652:15)
    at Compiler.Compile (/Users/hajimekurita/.nodebrew/node/v12.4.0/lib/node_modules/nectarjs/compiler/native/compiler.js:394:3)
    at /Users/hajimekurita/.nodebrew/node/v12.4.0/lib/node_modules/nectarjs/nectar.js:336:13
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:61:3) {
  status: 1,
  signal: null,
  output: [
    null,
    <Buffer >,
    <Buffer 49 6e 20 66 69 6c 65 20 69 6e 63 6c 75 64 65 64 20 66 72 6f 6d 20 2f 55 73 65 72 73 2f 68 61 6a 69 6d 65 6b 75 72 69 74 61 2f 74 6d 70 2f 2e 6e 65 63 ... 1510 more bytes>
  ],
  pid: 83126,
  stdout: <Buffer >,
  stderr: <Buffer 49 6e 20 66 69 6c 65 20 69 6e 63 6c 75 64 65 64 20 66 72 6f 6d 20 2f 55 73 65 72 73 2f 68 61 6a 69 6d 65 6b 75 72 69 74 61 2f 74 6d 70 2f 2e 6e 65 63 ... 1510 more bytes>
}
       1       1       2

real	0m0.005s
user	0m0.002s
sys	0m0.004s

It's a Clang error, i will check it

Related to #66

I reverted the string mgmt, i will update it to support more iteration as the fix i pushed was not supported by clang

At least compilation, it becomes O.K.
Multi tier lopp has still problem.
Reporting is just recording purpose though you know it.
cat c.js;nectar --version; nectar  c.js;time ./c|wc
for(let i=0;i<100000;i++){
	for(let y=0;y<10;y++){
		console.log("a");
	}
}
NectarJS v0.5.32
[*] Generating source file
[*] Compiling
  124993  124993  249986

real	0m1.240s
user	0m1.066s
sys	0m0.527s

thank you very much, i found the issue and corrected it, i will push the update soon

2c7eccf shoud solve the problem, can you give me your feedback ?

Hi, thanks for your fixing.
Here is the test result.

Loop problem was solved
But in more tests for loop, I found problem of how to deal with large number. <= Test case 4)

Please confirm.
Thanks!
========

OK: just console.log

FILE=a.js;cat $FILE;time node $FILE|md5;time deno $FILE|md5;nectar --version;nectar --preset speed $FILE;time ./a|md5
console.log("B");

30cf3d7d133b08543cb6c8933c29dfd7

real	0m0.072s
user	0m0.051s
sys	0m0.020s
30cf3d7d133b08543cb6c8933c29dfd7

real	0m0.038s
user	0m0.020s
sys	0m0.013s
NectarJS v0.5.33
[*] Generating source file
[*] Compiling
30cf3d7d133b08543cb6c8933c29dfd7

real	0m0.006s
user	0m0.003s
sys	0m0.004s

OK: Simple loop

 FILE=b.js;cat $FILE;time node $FILE|md5;time deno $FILE|md5;nectar --version;nectar --preset speed $FILE;time ./b|md5
for(let i=0;i<100000;i++){
		console.log("a");
}
484c67d5c84f5d502bf56e01a51066df

real	0m0.663s
user	0m0.699s
sys	0m0.374s
484c67d5c84f5d502bf56e01a51066df

real	0m0.307s
user	0m0.187s
sys	0m0.227s
NectarJS v0.5.33
[*] Generating source file
[*] Compiling
484c67d5c84f5d502bf56e01a51066df

real	0m1.090s
user	0m0.978s
sys	0m0.417s

OK: Tier 2 loop

FILE=c.js;cat $FILE;time node $FILE|md5;time deno $FILE|md5;nectar --version;nectar --preset speed $FILE;time ./c|md5
for(let i=0;i<100000;i++){
	for(let y=0;y<10;y++){
		console.log("a");
	}
}
050cf373c7c785c764c02e6649e6082e

real	0m5.510s
user	0m5.162s
sys	0m3.215s
050cf373c7c785c764c02e6649e6082e

real	0m2.815s
user	0m1.579s
sys	0m2.027s
NectarJS v0.5.33
[*] Generating source file
[*] Compiling
050cf373c7c785c764c02e6649e6082e

real	0m11.372s
user	0m9.789s
sys	0m4.225s

Bad: With more nest & output number

FILE=e.js;cat $FILE;time node $FILE|md5;time deno $FILE|md5;nectar --version;nectar --preset speed $FILE;time ./e|md5
let num = 0;
for(let i=0;i<10;i++){
	num = i+1;
	for(let y=0;y<10;y++) {
		num *= (y+1);
		let x = 1;
		while(x<10){
			num *= (x+1);
			console.log(num);
			x++;
		}
	}
}
d6bf1ec4936f9065b4f4a8e14be3e4ce

real	0m0.091s
user	0m0.071s
sys	0m0.023s
d6bf1ec4936f9065b4f4a8e14be3e4ce

real	0m0.118s
user	0m0.030s
sys	0m0.029s
NectarJS v0.5.33
[*] Generating source file
[*] Compiling
7988b05781f6502c9bf5684bcf28de11

real	0m0.010s
user	0m0.006s
sys	0m0.008s

Thank you for your feedback,
i will add a big number lib for managing big number, could you open a new issue for this ?

I created new issue
https://github.com/NectarJS/nectarjs/issues/81
For this loop issue, I can say the problem was resolved.
Thanks for you work!


Master Scheduler API

Looks good. Looks like the repo is now on 0.19.13, so you'll need to bump it to 0.19.14.


Stopping on invisible break point

I have a bug where a break point is being hit that is not visibly set. There are no breakpoints listed in the break points list either. Attempted to reinstall the plug in but that didn't work. Cleared cookies on browser that also didn't work. Also attempted to switch port from 9000 to 9001. Not sure if this is an XDebug issue or and issue with the plug-in.

Thanks, worked for me too!

Worked for me also, Thanks!


add 'dbt-cloud run cancel' command

Description & motivation
Hey @stumelius, sweet package 😄  - keen to contribute to #29
Could use some help:

Adding tests.
Figuring out what to do when the --run-id targets a run that has already succeeded / errored - should we check that a job is currently running / queued / starting before cancelling?

Checklist

[ ] I have written unit tests for new features (e.g., a new command test case in conftest.py)
[ ] I have written integration tests for new features (e.g., a new step in the CI workflow)
[x] I have added descriptions to new commands and arguments
[ ] I have updated the README.md (if applicable)

The PR looks great, nice work @jeremyyeo! :)

Adding tests : You can add a new command test case in conftest.py. You'll need to create an example response JSON file in the tests/data/ folder (e.g., tests/data/run_cancel_response.json). Let me know if you need more assistance :)

Figuring out what to do when the --run-id targets a run that has already succeeded / errored - should we check that a job is currently running / queued / starting before cancelling?: If the run has finished (success or error) the cancel request will just return a success response, right? I don't see any problem with that.


Conversational Retrieval QA with sources cannot return source

System Info
ConversationalRetrievalChain with Question Answering with sources
llm = OpenAI(temperature=0)
question_generator = LLMChain(llm=llm, prompt=CONDENSE_QUESTION_PROMPT)
doc_chain = load_qa_with_sources_chain(llm, chain_type="map_reduce")

chain = ConversationalRetrievalChain(
    retriever=vectorstore.as_retriever(),
    question_generator=question_generator,
    combine_docs_chain=doc_chain,
)

if i set the chain_type to "refine". it will not return sources.
Who can help?
No response
Information

[ ] The official example notebooks/scripts
[ ] My own modified scripts

Related Components

[ ] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[X] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
just like the turtial code.
Expected behavior
i want the 'refine' chain return sources.

langchain version: 0.0.218


Minor cleaning of .gitignore files in tests folder

/runtime/cache/* already ignored by file /tests/runtime/.gitignore
/tests/runtime/assets/ already stays in place due to file /tests/runtime/asstes/.gitignore

Merged. Thanks!


Make 2018 the default ecmaVersion for rules relying on parserOptions

Some core rules (and potentially custom rules in the ecosystem) rely on checking parserOptions in the rules themselves. Technically, since Babylon always parses the latest (including experimental) syntax, this should be set to the latest ESLint supports (currently 2018).

I don't think this has any effect -- ESLint copies the parserOptions object before passing it to parsers.

Oh, I see. I had forgotten it.
But, I think that it's given to eslint-scope.

https://github.com/babel/babel-eslint/pull/559/files#diff-3ab10361493aeb949966224850773473R320
https://github.com/babel/babel-eslint/pull/559/files#diff-2d0b8df824f212d55b29824f29bf4b48R364


Compiling fails on latest master

Version Information:

Version: 0.11.1

Macbook running Catalina 10.15.5, rustc 1.44.1 (c7087fe00 2020-06-17)
Description:

Compiling fails, giving:
 Compiling horust v0.1.1 (/Users/t0mgs/IdeaProjects/Horust)
error[E0432]: unresolved imports `libc::prctl`, `libc::PR_SET_CHILD_SUBREAPER`

src/horust/mod.rs:14:12
   |
14 | use libc::{prctl, PR_SET_CHILD_SUBREAPER};
   |            ^^^^^  ^^^^^^^^^^^^^^^^^^^^^^ no `PR_SET_CHILD_SUBREAPER` in the root
   |            |
   |            no `prctl` in the root

error[E0425]: cannot find function `execvpe` in module `nix::unistd`
   --> src/horust/runtime/process_spawner.rs:149:18
    |
149 |     nix::unistd::execvpe(program_name.as_ref(), arg_cptr.as_ref(), env_cptr.as_ref())?;
    |                  ^^^^^^^ help: a function with a similar name exists: `execve`
    |
   ::: /Users/t0mgs/.cargo/registry/src/github.com-1ecc6299db9ec823/nix-0.16.1/src/unistd.rs:734:1
    |
734 | pub fn execve(path: &CStr, args: &[&CStr], env: &[&CStr]) -> Result<Void> {
    | ------------------------------------------------------------------------- similarly named function `execve` defined here

error: aborting due to 2 previous errors

Some errors have detailed explanations: E0425, E0432.
For more information about an error, try `rustc --explain E0425`.
error: could not compile `horust`.

Haven't actually figured out what these deps are, just wanted to persist this if anyone else has the same issue.
@FedericoPonzi gettin' late round these parts, if you can take a look that would be great.

Unfortunately as of today, horust will only compile on Linux.
Libc contains low bindings to *nix's libc, and the nix crate is a "safe" wrapper around those low level bindings.
If for example you look here:
https://docs.rs/nix/0.17.0/src/nix/unistd.rs.html#772
#[cfg(any(target_os = "haiku",
          target_os = "linux",
          target_os = "openbsd"))]

This is missing the "macos" target.
I'm not sure if it would make sense to support Mac in the near future, but if you wish you can try to add it but I'm not sure how much effort would be required to implement it.

Well, it feels to me that compiling a project you're working on # is probably a good thing to have! ;)
I could set up a small script to run the compilation on a container and run horust inside it, but that feels like a lot of "going around" the problem.
Let me dive a bit deeper to see whether there's already an attempt at making it work for Darwin and see where we go from there.
Haven't dove into the code yet, but is that crate vital or could we swap it?

Well, it feels to me that compiling a project you're working on # is probably a good thing to have! ;)

Indeed!

I could set up a small script to run the compilation on a container and run horust inside it, but that feels like a lot of "going around" the problem.

I think a Makefile which wraps cargo would work here. "make build|test|run". There is already a dockerfile, so it should be something quick to do (modulo the ccache which is not there at this moment).

Let me dive a bit deeper to see whether there's already an attempt at making it work for Darwin and see where we go from there.
Haven't dove into the code yet, but is that crate vital or could we swap it?

I don't think so. The supervision stuff could probably be abstracted away from the os, but some bits are kind of "low level" so they need to know some details of the os in order to work properly. Also, nix /libc are supported on macos, so I think it's just a matter of replacing linux specific function to either more generic functions (e.g. the execvpe error you got), or provide substitutions for Mac.
I think you could search for libc/nix used functions, and check the docs for each function and try to understand if they're compatible with Mac or how to integrate/replace them. In the best case scenario, as soon as you fix those two errors everything might build properly (this exaplins the issue related with execvpe).
Also, if you want to go with this second option, you might want to update the CI to build also for macos, create a pr with all the changes. I could also help if we have ci and the pr ready.

Alright, sounds reasonable! Will take a look tonight

Looking at libc's crate docs it seems that there's a script that's used in CI, intended to make sure the currently installed rust toolchain can compile for target X. I'll get back to this in a second.
Let's first tackle the libc issue. I can see libc compiling properly, but after compilation prctl and PR_SET_CHILD_SUBREAPER are not available (note that the latter is an optional first argument of the former).
Here's the usage of both in the current branch: https://github.com/FedericoPonzi/Horust/blob/e38dc967dd05676f8a19633a7e0371a08245eaa1/src/horust/mod.rs#L54-L58
Looking at the docs for the crate's prctl here is not super useful, since it's just a binding to the low-level function. Looking at the actual prctl docs here shows that it's used to control the calling process / thread. Specifically, when provided the PR_SET_CHILD_SUBREAPER (from the docs):
          If arg2 is nonzero, set the "child subreaper" attribute of the
          calling process; if arg2 is zero, unset the attribute.

          A subreaper fulfills the role of init(1) for its descendant
          processes.  When a process becomes orphaned (i.e., its
          immediate parent terminates), then that process will be
          reparented to the nearest still living ancestor subreaper.
          Subsequently, calls to getppid(2) in the orphaned process will
          now return the PID of the subreaper process, and when the
          orphan terminates, it is the subreaper process that will
          receive a SIGCHLD signal and will be able to wait(2) on the
          process to discover its termination status.

Awesome SE answer about subreapers here, btw.
Since I can see the libc compiling properly, yet I don't have any prctl in the root, I took a look at libc crate's available platforms page, and it does not look like darwin or macos is there.
I need to go down the rabbit hole a bit more, but it's getting late again... time flies when you're having fun:)
(Also, I know this is all basic stuff - but these types of issues often turn out to be great blog post prompts, so I'm pre-doing all the work now:) ).

Back at it now.
Even if I end up fixing the execvpe issue, I'm still left with prctl which doesn't exist on Mac OS, per here.
I think I'm gonna focus on getting this compiled in a container, and see how painful it is to develop with.

I would like to provide few interesting points:

Creating an init system compatible with all the *nix systems is hard if not impossible. It would probably require many flags to work properly on every system, and I don't think it's something we should bother with at this time.
prctl is for for using some linux kernel specific features which are not present in Macos. It's also one of the main reasons why when you run docker on Mac, under the hood it spawns a linux VM on which it will run your containers.
In this particular instance, prctl is used for enabling the PR_SET_CHILD_SUBREAPER. I though it would have been useful for people who wanted to run horust as a normal process. But it's not really needed, everything should work as fine even if you put it behind a not(mac) flag.
Since you might encounter other issues and for now we're foremost targeting docker containers, I think it would be easier, faster and better if you could stick with the docker container. I would advise to update the makefile with your commands.

No Mac specifics for me, then. Back soon with a spruced-up Makefile.

So, unsurprisingly, just building the image every time I make a change to a file takes forever (12+ minutes to be exact, between updating the crate index, downloading crates and compiling them). Need a way to cache compiled crates in between builds, and (possibly) refrain from updating the crates index as I go along.
https://stackoverflow.com/questions/58473606/cache-rust-dependencies-with-docker-build is a good start, and the follow up https://blog.mgattozzi.dev/caching-rust-docker-builds/ that I got from there. Hacking it in now.

Before diving too deep here, check out https://benjamincongdon.me/blog/2019/12/04/Fast-Rust-Docker-Builds-with-cargo-vendor/

Also - https://github.com/denzp/cargo-wharf for "magic" rust image dep cache builder

(fixed by #41)


[Feature Request]系统属性功能增强，支持应用模块自定义配置

Checklist

[X] I searched exising issues and no one else requests similar feature.
[X] I think that 25%+ users are positive towards this feature.

Describe the feature
用于各个模块的自定义配置
模块名.xxx = aaa
Additional context
No response

Config 扩展 get set

改用json？

#1282

等待commons-configuration升级吧
目前改造后仅仅对jlink有提升，额外配置提升不大

Hello @unknowIfGuestInDream. This issue is marked as deprecated and closed.


Incompatible mods(Create & Sound Physics Remastered )

Describe the Bug
Fabric Loader log:
Incompatible mods found!
net.fabricmc.loader.impl.FormattedException: Some of your mods are incompatible with the game or each other!
A potential solution has been determined, this may resolve your problem:
	 - Replace mod 'Create' (create) 0.5.1-f-build.1417+mc1.20.1 with version 0.5.1-f-build.1417+mc1.20.1 that is compatible with:
		 - sound_physics_remastered 1.20.1-1.4.5
More details:
	 - Mod 'Create' (create) 0.5.1-f-build.1417+mc1.20.1 is incompatible with any version of mod 'Sound Physics Remastered' (sound_physics_remastered), but a matching version is present: 1.20.1-1.4.5!
	at net.fabricmc.loader.impl.FormattedException.ofLocalized(FormattedException.java:51)
	at net.fabricmc.loader.impl.FabricLoaderImpl.load(FabricLoaderImpl.java:195)
	at net.fabricmc.loader.impl.launch.knot.Knot.init(Knot.java:146)
	at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:68)
	at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)

Reproduction Steps
Start the game with mod
Expected Result
I wanted to see a game that started and works)
Screenshots and Videos
No response
Crash Report or Log
No response
Operating System
Windows 11
Mod Version
0.5.1f
Minecraft Version
1.20.1
Other Mods
No response
Additional Context
No response

Duplicate issue, search for your issue before opening a new one


Defer bind() when a view is not yet loaded

Background
ReactorKit was not well-considered for a storyboard. Assigning a reactor to a view makes bind(reactor:) get called. When using storyboard it occurs a runtime error about a force unwrapping of optionals. It's because the timing of the bind(reactor:) is prior to a storyboard initialization. This PR provides a better storyboard support by deferring a binding when a view is not yet loaded.
Summary

Defer a bind(reactor:) execution until a view is loaded.
Add tests for deferring binding.
Update examples to assign reactors outside of view controllers.

Codecov Report

Merging #23 into master will increase coverage by 1.08%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #23      +/-   ##
==========================================
+ Coverage   90.27%   91.35%   +1.08%
==========================================
  Files           4        4
  Lines          72       81       +9
==========================================
+ Hits           65       74       +9
  Misses          7        7

Impacted Files
Coverage Δ

Sources/View.swift
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Is anywhere example repo with latest remix 2.x + mdx-bundler?

Hi guys, I am struggling to implement mdx-bundler into remix 2.3. I read "Usage" in README.md but I don't know how to integrate it into remix (I am also new in remix). Will it work also with vite?
Is anywhere example repo with latest remix + mdx-bundler or article or video tutorial? Thanks. I was not able to find it.

I've been looking for a long time, too. I finally found the author's blog and the file structure was what I was looking for.
https://github.com/kentcdodds/kentcdodds.com/tree/main

I've also put a repro for my issue up that seems to work: https://stackblitz.com/edit/remix-run-remix-cqytcp


Insane reconnect madness in RR and TPPI

It'd seem either the Sender or Reader thread of the connection is crashing, causing a reconnect without actually closing the old connection. This causes many duplicate connections and crazy nicks like XYZ____________.
Make sure that connections are closed properly even when crashing and see if we can get logs of the crash to fix that one itself too.

Haven't seen anyone experiencing this in a while now in both #PlayTPPI and #rr, so since the core issue that caused the duplicate connections is fixed I'm closing this.


[WFLY-6144] EJB static client interceptors

https://issues.jboss.org/browse/WFLY-6144
https://issues.jboss.org/browse/EAP7-475
Please make sure your PR meets the following requirements:

[ ] Pull Request title is properly formatted: [WFLY-XYZ] Subject or WFLY-XYZ Subject
[ ] Pull Request contains link to the JIRA issue(s)
[ ] Pull Request contains description of the issue(s)
[ ] Pull Request does not include fixes for issues other than the main ticket
[ ] Attached commits represent units of work and are properly formatted

For bigger changes, major and minor component upgrades make sure your PR also meets following requirements:

[ ] Pull Request requires a change to the documentation
[ ] Documentation have been updated accordingly
[ ] Tests were added to cover changes

For new features ensure as well:

[ ] Analysis was done
[ ] Test Plan has been done
[ ] Tests were verified in advance

If you are not an active contributor of the WildFly project you can request sponsorship by one of the members to help guide you through the process.

There were basic tests failures after EjbSecurityDomainSetup was moved to shared project. Fixed.

I can't reproduce errors. Retest this please.

Retest this please

retest this please

for now, I cannot reproduce failing tests

@tadamski SecurityAuditingTestCase seems to fail across several test runs

SecurityAuditingTestCase works ok locally as well

@tadamski @kabir @jamezp @luck3y There are SecurityAuditingTestCase failures on other PRs too.
https://ci.wildfly.org/project.html?tab=testDetails&testNameId=-8471193340810971695&projectId=WF&order=TEST_STATUS_DESC
So if we keep seeing intermittent failures for this PR, let's discuss in wildfly-developers.

At this point, despite what may be shown in the CI results, this PR has passed on all jobs but one, where it ran out of time during mixed-domain testing, which we ignore if those pass on other runs.
So please don't kick off any other runs for this unless the code changes. Save CI for other uses.
If @kabir approves it's ready for merge. I believe he was just looking for some subsystem test stuff, which I see now.

@bstansberry Current failures are likely to be that unrelated dependency convergence problem I just mentioned in Zulip and on mail


Update dependencies of library

For potential security vulnerability in one of our dependencies.

I'm grateful for your polite work!


Document the problem with clang-format version

Why
After we use more concepts in the project, the format CI often fails and it is confusing. Document the related behavior to avoid the confusion as much as possible.
What is changing
Example

https://github.com/marketplace/actions/clang-format-check
这个能行么，看上去好像是复用别人写好的
https://github.com/jidicula/clang-format-action

https://github.com/marketplace/actions/clang-format-check
这个能行么，看上去好像是复用别人写好的
https://github.com/jidicula/clang-format-action

换成 pip3 install clang-format   好像就行了


CI: Test python 3.13

Python 3.13 has been released a couple days ago, let's test it!

Great, shall we squash and merge?


feat(GUI): add progress gauges for multi-writes

We add a new progress page where we display progress gauges or bars for
multi-writes. When there are too many gauges they change into bars.
Changelog-Entry: Add a progress page and progress gauges/bars for
multi-writes.
Change-Type: minor

Based on #1744. The codebase here isn't very clean yet while we work on the foundation of the functionality and the styles.

@Shou Can you post screenshots?

These are the design sketches, for reference purposes:

Current status: functional, UX isn't quite perfect, styles are very close to done, code isn't cleaned up
After make electron-develop you have to run npm install because of some shrinkwrap issues. To get back from the progress page, click the settings cog and then go back – hacky workaround!


Symlinked zips

Added arm64 for catalyst
Fixed zip with symlinks

Thank you! PR merged and re-tagged.


SSH access: workspace managers key injection, update laboperator rbac

Description
This PR updates the permission of Laboperator so that it is possible to retrieve the related tenant and workspace managers.
In addition it brings the feature of retrieving also the workspace managers keys in order to inject them in the VM.
It also fixes the RBAC of bastion-operator, since the list action is not performed anymore, the permission to get is granted instead.
How Has This Been Tested?
At the moment no tests have been performed, apart from a successful build and run of the operator.

/merge

/merge


Adding support for aiida-atomistic

in pseudo and cutoff we introduce the naming LegacyStructureData for th orm.StructureData.
two additional tests, triggered only when we have atomistic installed (HA is True).

Hi @sphuber , thanks a lot for the very useful comments, I think I addressed all of them! Let me know if any other modification/fix is needed


publich core as NPM package?

Would be really cool if this could be published as a package
would like to integrate this into markdown-processors, so maps can be written down in repos and then have revisions tracked

Do you have any examples of something you've installed this way? Maybe the syntax highlighter portion?

@ChristianDavis perhaps an npm package isn't required, if there was an endpoint that could be hit with the UML which returned the map that'd be pretty useful for embedding into markdown documents
variations of this approach are outlined here and here

https://www.npmjs.com/package/wmlandscape
Published as part of the build pipeline with every new version.


Add a defi project.

OmniBTC is an omnichain financial platform for web3,including omnichain swap and BTC omnichain lending.

format corrected

I'll close this PR first, and then submit it when we're ready to open source the code


(IT Infrastructure) Shutdown or recreate nominatim instance

The current nominatim instance is just a hack. We need to recreate it or delete it if not used.
Change the protocol to HTTPS in the backend.

@klinzo I created this so we do not forget

This is also relevant for deciding on an expiration date for the geocoding cache: https://github.com/digitalfabrik/ehrenamtskarte/pull/439#discussion_r780224454

In photon it is not possible to search for postal codes or restrict the search data to a specific country without additional configuration. I am not sure how easy it is to configure it accordingly but without it we'd need to change the whole geocoding logic as the current way won't work anymore.
Example postal code search: https://photon.komoot.io/api?q=86161
https://github.com/komoot/photon#customized-search-data

If you need search data in other languages or restricted to a country you will need to create your search data by your own. Once you have your Nominatim database ready, you can import the data to photon.

In photon it is not possible to search for postal codes or restrict the search data to a specific country without additional configuration. I am not sure how easy it is to configure it accordingly but without it we'd need to change the whole geocoding logic as the current way won't work anymore.
Example postal code search: https://photon.komoot.io/api?q=86161
https://github.com/komoot/photon#customized-search-data

If you need search data in other languages or restricted to a country you will need to create your search data by your own. Once you have your Nominatim database ready, you can import the data to photon.

Alright :D then lets stick to nominatim. We could just makr our artifacts public and let others benefit from our processing power :)

Alright :D then lets stick to nominatim. We could just makr our artifacts public and let others benefit from our processing power :)

Is it feasible to keep nominatim up to date/maintain it? You mentioned this was too much effort.

I mean it is a lot of work and maintanance, but if it has to be done :D

I'll try to come up with another solution :)

The thing is we already have to generate the maps once per year. I could reuse the setup for nominatin
The only thing is that we need to keep up with nominatim breaking changes. But this is probably not a huge problem.

high-priority: Should be done before I forget about the nominatim creation :D

We should probably add basic auth for now, at least before this project gets more attention.


SAP HANA XS Advanced, Creating an HDI Module

Tutorial URL: https://developers.sap.com/tutorials/xsa-hdi-module.html
Please specify the step you are referring to
Step 2: Create CDS Table
Save the artifact after entering this code. Go back to the graphical editor to gain better clarity of the data model.
Save the artifact after entering this code **close-> open tab or refresh  in (SPS03)**
Go back to the graphical editor to gain better clarity of the data model

I'm not having this problem in SPS03 (and haven't seen it in other people's instances), if you're having interface problems on HXE please post in answers.sap.com . Otherwise, I would create an incident. Thanks!


extract persistence event handling into standalone functions

for readability it would be nice to have this code in standalone functions
https://github.com/paradigmxyz/reth/blob/c4aae6db361d2ac33fed18f25bb50158907723ee/crates/engine/tree/src/persistence.rs#L63-L73
like on_remove_blocks, on_save_blocks etc.

@mattsse, can we maintain these functions within impl?

yes


Cognito Federation with Azure

Hi,
I've recently deployed AMC Uploader and setup the cognito OIDC federation with Azure. But it doesn't seems work properly as I want.
Once I login with Azure, I get redirected to the Uploader login page, and have to enter usename and password.
I've check the web application code. I thought if I want to use Azure to connect to AMC Uploader, the configuration should be in amplify auth.
Could we have this feature  available soon? Otherwise, do you have any other solution or advices on this subject?
Thanks for your response!

Hi @xiyue-55, federating with Azure would be outside the scope of what we can directly support for this solution currently. However, in the 3.0 release coming this spring, we will be switching to the Cognito Hosted UI for authentication, which should be easier for you to use for federating with another identity provider. We will also add this use-case to our backlog and we'll explore if it is something we want to start supporting.


Set up the environment

I installed the react-toolbox lib using the npm install command, and i have the following set up in my webpack.config
var webpack = require("webpack");
var path = require('path');

module.exports = {
    entry: {
        //put ur bundle files here.
        login: './static/js/bundles/login.js',
        factigisDashboard: './static/js/bundles/factigisDashboard.js',
        factigisFrontoffice: './static/js/bundles/factigisFrontoffice.js',
        factigisCarta: './static/js/bundles/factigisCarta.js',
        factigisBackoffice: './static/js/bundles/factigisBackoffice.js',
        factigisBackoffice2: './static/js/bundles/factigisBackoffice2.js',
        vendor: [
        // put your third party libs here
        ]
    },
    output: {
        path: path.join(path.join(__dirname, 'dist'), 'js'),
        filename: '[name].js',
        libraryTarget: "amd"
    },
    resolve: {
        extensions: ['', '.webpack.js', '.web.js', '.js', '.jsx']
    },
    module: {
      loaders: [
       {
         test: /\.(js|jsx)$/,
         exclude: /node_modules/,
         loader: 'babel',
         query: {
           presets: ['react', 'es2015', 'stage-2']
         }
       }
     ]
    },
    externals: [
        function(context, request, callback) {
            if (/^dojo/.test(request) ||
                /^dojox/.test(request) ||
                /^dijit/.test(request) ||
                /^esri/.test(request)
            ) {
                return callback(null, "amd " + request);
            }
            callback();
        }
    ],
    devServer: {
      inline: true,
      port: 443,
      host: "<IP_ADDRESS>"
    },
    devtool: 'source-map'
};

Also i want to render the AppBar component in my app, like this:

import {AppBar} from 'react-toolbox/lib/AppBar';
...

render(){

      return (
        <AppBar fixed flat>

                  <input className="login__input" ref="username" type="text" placeholder="miusuario"  />
                  <input className="login__input" ref="password" type="password" placeholder="password" onKeyPress={this.handleKeyPress.bind(this)}  />

                  <button onClick={this.onClick.bind(this)}
                    className="login__submit" title="Entrar " type="button" >
                     Entrar
                  </button>

© 2016 Pérdidas y GIS

          </AppBar>

    );
  }

But im getting errors when i render my component.

How can i fix this ? im really interested to use this awesome lib :(

@darklilium you have to setup to bundle the sass files with webpack and the toolbox loader
http://stackoverflow.com/questions/34969914/webpack-not-loading-scss-with-react-toolbox
https://github.com/react-toolbox/toolbox-loader

@darklilium You have to instal immutability-helper too (first error). You can install it with npm install --save immutability-helper

I set up the config like the website but im getting some errors, what am i missing? Sorry im pretty new on using webpack.
var webpack = require("webpack");
var path = require('path');

module.exports = {
    entry: {
        //put ur bundle files here.
        login: './static/js/bundles/Login.jsx',
        vendor: [
        // put your third party libs here
        ]
    },
    output: {
        path: path.join(path.join(__dirname, 'dist'), 'js'),
        filename: '[name].js',
        libraryTarget: "amd"
    },
    resolve: {
        extensions: ['', '.webpack.js', '.web.js', '.js', '.jsx']
    },
    module: {
      loaders: [
       {
        test: /\.(js|jsx)$/,
        exclude: /node_modules/,
        loader: 'babel',
        query: {
          presets: ['react', 'es2015', 'stage-2']
        }
      },
      {
        test: /\.s?css$/,
            loaders: ['style', 'css', 'sass'],
             exclude: /(node_modules)\/react-toolbox/
      },
      {
        test: /(\.scss|\.css)$/,
          include : /(node_modules)\/react-toolbox/,
          loaders : [
            require.resolve('style-loader'),
            require.resolve('css-loader') + '?sourceMap&modules&importLoaders=1&localIdentName=[name]__[local]___[hash:base64:5]',
            require.resolve('sass-loader') + '?sourceMap'
          ]
      }
     ]
    },
    externals: [
        function(context, request, callback) {
            if (/^dojo/.test(request) ||
                /^dojox/.test(request) ||
                /^dijit/.test(request) ||
                /^esri/.test(request)
            ) {
                return callback(null, "amd " + request);
            }
            callback();
        }
    ],
    devServer: {
      inline: true,
      port: 443,
      host: "<IP_ADDRESS>"
    },
    devtool: 'source-map'
};

@darklilium you have to see your stack trace... cannot find module 'style-loader' so you have to install it.
npm install --save-dev style-loader

@darklilium maybe you will have to install and if you have starting the project use https://github.com/Nazariglez/react-toolbox-boilerplate and this https://github.com/react-toolbox/react-toolbox-example or use an example how webpack is setup

Thanks guys, actually i had to install 3 new node components that i didnt have. Not im able to use the elements on my config, but i still not being able to see them correctly with the css.
I want to have a .css file with all the css code that im going to use for the page. Is there a way to do it using sass?
Now im having a sass file like: login.scss with this,
@import "node_modules/react-toolbox/lib/button/theme.scss";
@import "node_modules/react-toolbox/lib/colors.scss";
but i still dont know why i cannot see my page correctly.

Any help?

did you add this lines https://github.com/react-toolbox/react-toolbox-example/blob/master/webpack.config.js#L39?

I added them like this.
var webpack = require("webpack");
var path = require('path');

module.exports = {
    entry: {
        //put ur bundle files here.
        login: './static/js/bundles/Login.jsx',
        vendor: [
        // put your third party libs here
        ]
    },
    output: {
        path: path.join(path.join(__dirname, 'dist'), 'js'),
        filename: '[name].js',
        libraryTarget: "amd"
    },
    resolve: {
        extensions: ['', '.webpack.js', '.web.js', '.js', '.jsx']
    },
    module: {
      loaders: [
       {
        test: /\.(js|jsx)$/,
        exclude: /node_modules/,
        loader: 'babel',
        query: {
          presets: ['react', 'es2015', 'stage-2']
        }
      },
      {
        test: /\.s?css$/,
            loaders: ['style', 'css', 'sass'],
             exclude: /(node_modules)\/react-toolbox/
      },
      {
        test: /(\.scss|\.css)$/,
          include : /(node_modules)\/react-toolbox/,
          loaders : [
            require.resolve('style-loader'),
            require.resolve('css-loader') + '?sourceMap&modules&importLoaders=1&localIdentName=[name]__[local]___[hash:base64:5]',
            require.resolve('sass-loader') + '?sourceMap'
          ]
      }
     ]
    },
    sassLoader: {
      data: '@import "theme/_config.scss";',
      includePaths: [path.resolve(__dirname, './src/app')]
    },
    externals: [
        function(context, request, callback) {
            if (/^dojo/.test(request) ||
                /^dojox/.test(request) ||
                /^dijit/.test(request) ||
                /^esri/.test(request)
            ) {
                return callback(null, "amd " + request);
            }
            callback();
        }
    ],
    devServer: {
      inline: true,
      port: 443,
      host: "<IP_ADDRESS>"
    },
    devtool: 'source-map'
};

But im having the following errors:

Do you have the file theme/_config.scss?

Well, i have this set up, (i make a rollback on how i had my environment, so i havent add anything about this lib yet)
MyEnv.zip
The thing is, im using arcgis js lib and each time when i want a prod build i make the npm run prod:build command who allows me to get all my files ready to put in my prod server (css, html and js).
I still dont know how to use the lib with my set up, im reading the installation in the website but to me it is not too clear yet.

You don't have to run each time only when you will go to production. First try to use only the project with one of the boilerplates then integrate with your project.

I was trying to use this (i clone the repo) but it isnt working..
https://github.com/Nazariglez/react-toolbox-boilerplate


Circular radar chart with labels

Hi,
Not really an issue but more of a little new feature: I needed to have a circular radar chart but with labels outside the chart like the regular radar chart (see the result below), and I couldn't find a way to do this with the available options.

Expected result
After taking a look into the code I figured that it couldn't be done when the parameter scale.lineArc is true... this being the parameter that sets the chart circular :(
To fix this I added a new boolean parameter so I can pass the condition when scale.lineArc is true,  scale.lineArcWithLabels, and changed a bit the code in LinearRadialScale.draw by replacing:
if (!opts.lineArc) {
[...]
}

with:
if (!opts.lineArc || opts.lineArcWithLabels) {
[...]
}

It was enough for me, there is maybe a cleaner way to do this but I didn't dive much more than that into the code. Just suggesting a new feature here since I needed it!

That sounds like a good feature. I think there could be some improvements as you suggest, but off the top of my head I don't know what exactly they would be

@damienmoulard How did you create this chart ? Can you paste the configuration settings if you have it now. Thanks

For people who want to switch from straight gridlines in the radar chart to circular ones:
options: {
                scale: {
                     gridLines: {
                        circular: true
                    }

I wrote a sample https://jsfiddle.net/5quzhwmc/1/
used:
options: {
    scale: {
      gridLines: {
        circular: true
      },
      angleLines: {
        display: true
      }
    }
  }


refactor: better import from node:fs/promises

Description
node v14 added a simpler import path for fs promises: fs/promises
Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the PR Title Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

I'm not really a fan of named imports of nodejs modules, as when it scales the API name has a higher chance of conflicting with local names, and it doesn't help with runtime perf (IIRC). But if others prefer this approach, I wouldn't mind too.

@bluwy it looks like right now we have a good mix between the two styles:
import { } from 'node:xxx' - 113 times
import obj from 'node:xxx' - 134 times
I think it would be good to have a preferred way in the Vite, and we can use the other when we see it would simplify things. I prefer named imports myself, maybe we could check with others in the team what they think is better here.

Thanks for the PR again @c0dedance, for the moment, we didn't reach a consensus of what is the best approach here. I think we are slowly moving towards using fs and fsp for fs checks. Let's close this PR for now.


Save mapped read strings and coordinates takes forever

In src/pangenome/pangraph.cpp I now have a function:
void Graph::save_mapped_read_strings(const string& readfilepath, \\
const string& outdir, const int32_t buff)

Which for each gene, finds the coordinates on the reads for each cluster of hits and creates a file with this segment of read output to it.
This function takes about 2 days (or more) to run on full K12 pangenome and 900X nanopore reads (compared to an hour and a half for the rest of the map code)

No longer relevant


setTimeLimit() not working for LocalSearchMetaheuristic.Value.GREEDY_DESCENT

What version of OR-tools and what language are you using?
Version: v7.5
Language: Java
Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP, Gurobi)
Routing Solver
What operating system (Linux, Windows, ...) and version?
Linux Ubuntu 18.04 LTS
What did you do?
We tried to set the setTimeLimit() value for the Routing solver, so that it return or stop finding optimal solution after that timeout (in seconds).
Please find the code snippet below:
RoutingSearchParameters searchParameters = main.defaultRoutingSearchParameters() 				.toBuilder()			                                 .setLocalSearchMetaheuristic(LocalSearchMetaheuristic.Value.GREEDY_DESCENT) 				.setTimeLimit(Duration.newBuilder().setSeconds(1).build()) 				.build();
What did you expect to see
The TSP solver should stop searching for optimum route after the set time limit is reached.
Example: We set the time limit to 1.0 sec
But the below o/p shows that the TSP is running beyond 1.0 sec.
Tsp ex time : 4.517
What did you see instead?
The TSP solver is continuing beyond the time set and the different timeout values in seconds are not working.
Make sure you include information that can help us debug (full error message, model Proto).
Anything else we should know about your project / environment

I have the same issue. Can some one throw some insights here @Mizux

Please ask on the mailing list, IIRC time limit is for the Local Search since it is checked each time a new solution is found.


Tidy up bits of logic, use class for Nametags

Tidies up a bit of logic, fixup a few formatting issues.

the force parameter in updatePlayer is used to force the update when the formatter changes in the config


TailwinPlay does not recognize "bg-primary" class name

Hi,
I tried on TailwindPlay with a simple Card here: https://play.tailwindcss.com/IiCmZ5EuXm and the "bg-primary" is not working. While the same html works as expected in CodePen with CDN css files: https://codepen.io/zemian/pen/jOBrpvR. Is there some configuration I need to enable to use these schematic role names in TailwindPlay?

Hi, You need to add colors to the config this way
module.exports = {
  plugins: [
    require('daisyui'),
  ],
  theme: {
    extend: {
      colors: require('daisyui/colors')
    },
  },
}

Reason:
DaisyUI adds colors to Tailwind if it finds tailwindcss installed as a dependency, If it can't find tailwindcss (let's say, you're using a fork of tailwind with different name or a similar project) it shows a warning on console, telling you how to extend color (like the code above)
You can't see the console log in Tailwind Play unless you open the browser console tho 😅
This functionality allows us to import colors by default, but if you don't have the tailwindcss installed as a dependency (if you're using a fork or a similar project with different name) you can still use the colors.
I will update the Tailwind Play example link in the docs. Thanks!

Ah, I see it works with your updated config now. Thanks!
Yes, updating the example config in your site's link (the one show at the bottom of your home page. eg: https://play.tailwindcss.com/RcIZd1Mwho) would be good for beginners so they don't think it's broken.
BTW, I think DaisyUI is a pretty cool project! I feel the the Tailwind can be pretty verbose on styling common UI components, and DaisyUI's built-in schematic role names make it easier to get started and be productive. I like how I can further customize the UI with direct Tailwind utility classes! This is pretty awesome. Keep up the good work!


Pokemon-Proto

Hi,
Where did you source this protofile? Is this what is needed to decode the player profiles etc? I see proto's here: https://www.reddit.com/r/pokemongodev/comments/4svl1o/guide_to_pokemon_go_server_responses/
Just curious what this one is.
Just trying to get some more clarity.
Great work on your project!

Hi :) atm I'm using the one from https://github.com/tejado/pokemongo-api-demo but I'm updating some fields in my own version


Privacy Policy link in Travelocity Application does not redirect to a privacy note.

Steps to re-create

Check out samples for v5.5.0-alpha from https://docs.wso2.com/display/IS550/Downloading+a+Sample

Register Travelocity as the Service Provider.

Follow the steps in Consent Management document.

Login to Travelocity, provider details for claims and user will be directed to following screen.

Click on Privacy Policy link.

Expected: User should be navigated to privacy note.
Actual: It redirects to the same page.
Type/Improvement
Affected/5.5.0-alpha
Severity/Major
Priority/High

This is already captured with https://github.com/wso2/product-is/issues/2398. Policy URL should be configurable for all SPs.


Contest deadline date is never set

Hi mangopay developers,
I am currently using your API for a client.
When I was testing the hooks for a dispute, I noticed that the Contest deadline date is always 'null'.
After a little debugging, I found that in com.mangopay.core.RestTool.java (line 747) there is a little bug.
if (fieldTypeName.equals(long.class.getName())) {        f.setLong(result, entry.getValue().getAsLong());  }
In the code above, you check for the primitive 'long' but there should be a check for a Long Object instead. As the primitive 'long' is not found, the Contest deadline date is never set.
This is an urgent issue for our application. Could this please be fixed as soon as possible?
Thanks you all for this great API!

Hey @WardStinissen, thanks for flagging this up. Would you be able to do a pull request with the fix? This would be the quickest way to get it resolved, but if not we'll get it sorted as soon as we can :-)

Hey, just to let you know that this has now been fixed with https://github.com/Mangopay/mangopay2-java-sdk/commit/3a523f6e8ae4e1c5dabfbcaaa8288a5a6b2f57af

@hobailey Thanks for the fast fix of this issue! :-)


Remove dependency on grunt

Given that there are very little reasons to keep using Grunt in modern Node.js ecosystem, consuming used libraries (such as JSHint) directly through npm might be more maintainable than using grunt with plugins.

Closing this due to no recent activity. If this is still a problem or you have questions please feel free to comment again and we can try to help further.

I'd totally be willing to review a PR for this if anyone wants to submit one!

Sorry, was a bit hectic on my side due to switching job and apartment. Will try to get to it this week.

@kibertoad No problem! Looking forward to it!!


JavaScript: Implement scaling of messages during upload

Currently, we don't scale messages during the upload. This is really a bummer because it leads to under-reported upload speeds. So, this is really critical to the first public release.

Implemented in #188


Moment js is not working in daylight savings and its showing the timezone as GMT instead of BST in UK

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information if applicable):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. firefox, safari]
Version [e.g. 22]

Moment-specific environment

The time zone setting of the machine the code is running on
The time and date at which the code was run
Other libraries in use (TypeScript, Immutable.js, etc)

Please run the following code in your environment and include the output:
console.log((new Date()).toString())
console.log((new Date()).toLocaleString())
console.log((new Date()).getTimezoneOffset())
console.log(navigator.userAgent)
console.log(moment.version)

Additional context
Add any other context about the problem here.

See https://github.com/moment/moment/issues/6111#issuecomment-1501105788
Also, next time you raise an issue, please fill in all the details requested.


URL Cleanup

This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener).
Fixed URLs
Fixed But Review Recommended
These URLs were fixed, but the https status was not OK. However, the https status was the same as the http request or http redirected to an https URL, so they were migrated. Your review is recommended.

http://network.pivotal.io/open-source (301) with 1 occurrences migrated to:
https://network.pivotal.io/open-source (https result ReadTimeoutException).

Fixed Success
These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended.

http://en.wikipedia.org/wiki/Percentile with 1 occurrences migrated to:
https://en.wikipedia.org/wiki/Percentile (https result 200).
http://redis.io/ with 1 occurrences migrated to:
https://redis.io/ (https result 200).
http://redis.io/documentation with 1 occurrences migrated to:
https://redis.io/documentation (https result 200).
http://redis.io/topics/license with 1 occurrences migrated to:
https://redis.io/topics/license (https result 200).
http://aspnetwebstack.codeplex.com/wikipage?title=Contributors with 1 occurrences migrated to:
https://aspnetwebstack.codeplex.com/wikipage?title=Contributors (https result 301).
http://docs.pivotal.io/spring-cloud-services/1-3/common/circuit-breaker with 1 occurrences migrated to:
https://docs.pivotal.io/spring-cloud-services/1-3/common/circuit-breaker (https result 301).
http://docs.pivotal.io/spring-cloud-services/1-3/common/circuit-breaker/ with 2 occurrences migrated to:
https://docs.pivotal.io/spring-cloud-services/1-3/common/circuit-breaker/ (https result 301).
http://download.oracle.com/javase/6/docs/api/java/util/concurrent/locks/Lock.html with 2 occurrences migrated to:
https://download.oracle.com/javase/6/docs/api/java/util/concurrent/locks/Lock.html (https result 302).

Ignored
These URLs were intentionally ignored.

http://localhost/ with 8 occurrences

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


Add support for SSL client certificates in MySQL and Postgres

Discussed in https://github.com/lovasoa/SQLpage/discussions/299

Originally posted by pettersillander May  2, 2024
Could implemeting (maybe optional?) encrypted connection between client and server help to ease adoption of SQLpage in diverse environments?
Quite a few networks (even closed) are encrypted connections only nowadays. As all the SQLpage supported dbms's support TLS natively it's seems rather cumbersome to use a tunnel for encryption.
Just wondering this after configuring SQLpage in existing environments...

https://github.com/lovasoa/sqlx-oldapi/pull/7

@pettersillander , can you test the latest builds and let me know if it works for you ?
The easiest is to test lovasoa/sqlpage:main on docker.


ZMQ2 core type

Add a new communication core (ZMQ_2), that uses a single PUSH/PULL socket for cores and reduces use of REQ/REP sockets.
This will alleviate the the possibility of running out of sockets if using a high number of federates on a single machine.    Basically copying the zmq core and adding in the necessary hooks so it is active.

For some reason, running with helics runner results in huge number of sockets. Investigating that issue.


Could you please elaborate on the buildContext

What is it? What is the default value: **?

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

ID: 0d9dbf88-7e55-d427-145e-d36b04fb197f
Version Independent ID: a3f30c00-817c-9c05-7a57-3f2bf618821e
Content: Docker task - Azure Pipelines
Content Source: docs/pipelines/tasks/build/docker.md
Product: devops
Technology: devops-cicd
GitHub Login: @thomps23
Microsoft Alias: shasb

I hit this today as well.  It is very common for buildContext to need to be set to non-default value.
The default buildContext (the Dockerfile directory if empty) will fail for a Dockerfile generated by Visual Studio for C# project that references another project in the solution.  In this case you have to set buildContext to nearest shared parent folder, which is the buildContext used by Visual Studio when building locally.  For me, when VS runs docker build locally the dockerfile is the 1st argument and buildContext is last argument.
docker build -f "c:\source\FooSln\FooProject\Dockerfile" ... "c:\source\FooSln"
For many C# projects the buildContext should be set to the the path to the .sln file in your git repo.
My team has one project that references projects outside the solution folder.  In this case keep moving up until you reach a "common parent" folder.  For us this is the root of the git repository.
If this is covered in the dotnet core docs or Visual Studio Docker docs then a link to this topic in those docs might be helpful.

@Lybecker The docker build command builds Docker images from a Dockerfile and a “context”. A build’s context is the set of files located in the specified PATH or URL. The build process can refer to any of the files in the context. For example, your build can use a COPY instruction to reference a file in the context.
It's advised to author a .dockerignore file to filter out the files and folders that should not be taken into account in the build context. This way the build context only contains the files and folders it really needs. This will help reduce the size of the file sent to docker daemon during build.
@yzorg The default value is set based on the most common scenario associated with most users using the Docker task. The input exists so that this default value can be overridden for edge cases such as the one mentioned by you. About including links to documentation for specific languages and projects, we wanted to keep the documentation generic and language agnostic

I'm curious why this is not captured in the actual documentation in stead of this comment/github issue?


[THEN] at end of xtensa-assembler.fs

Hello,
Why is there a [THEN] at the end of the xtensa-assembler.fs file?
Without [IF]..[ELSE], for me, this [THEN] is not justified.

Oops, yeah had meant to make adding the word conditional.
Fixed in:
https://github.com/flagxor/ueforth/commit/fe87f1574c4d33f6ce66a7199081e5838d7707fe


Update EditOrderCommand Usage with new detalis format

Updating message usage

Codecov Report

Merging #176 (e616edd) into master (6dee80b) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #176   +/-   ##
=========================================
  Coverage     67.37%   67.37%
  Complexity      688      688
=========================================
  Files           122      122
  Lines          2293     2293
  Branches        276      276
=========================================
  Hits           1545     1545
  Misses          626      626
  Partials        122      122

Impacted Files
Coverage Δ

...seedu/address/logic/commands/EditOrderCommand.java
93.65% <ø> (ø)

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 6dee80b...e616edd. Read the comment docs.


Add GROQ api

Would be nice to have the new and very fast Groq api also in the app and extension. Would be nice to offer a choice alternative from OpenAi.

second this suggestion. it is faster than openai.

I like that one!  ❤

If you're still search a Groq version,  here it's a Groq only fork.
Because patience is not my strength. ;)

PS:  I will stop the fork  if braden-w, maybe implement the Groq support by his own...

Closed in #236 !
Latest version has Groq support, just go to Settings/Transcriptions. Thank you @AlpSantoGlobalMomentumLLC  and @OLH21 for the inspiration!


Implement image scoring api to local-rest-scorer project

Implements newly introduced image scoring api to the local-rest-scorer project

bumps necessary versions
implement generation of new api code
introduces new controller, config, and converter classes to ensure proper Unimplemented error is sent as response to api request
add some simple tests.

Depends on: #314

@orendain fyi, separated pr for implementation of image scoring api in local-rest-scorer.

Closing as stale


Create Network Access Control Lists

https://github.com/Azure/azure-content/blob/master/articles/virtual-network/virtual-networks-acl-powershell.md

Hi @MAYAKARYA, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

@MAYAKARYA : Thanks for your contribution to the Azure documentation! The author, @azdocprs, has been notified to review your proposed change.

@jimdial Hi Jim Please review the proposed changes. Thanks.

@MAYAKARYA Please let me know what change you're proposing and why.  It's not clear to me in your proposal. Thanks

It's not clear to me what changes are suggested for this article.  Since there's been no reply from @MAYAKARYA then #PLEASE-CLOSE @jomolnar .


[Coverity CID :190630]Null pointer dereferences in /drivers/modem/wncm14a2a.c

Static code scan issues seen in File: /drivers/modem/wncm14a2a.c
Category: Null pointer dereferences
Function: net_pkt_setup_ip_data
Component: Drivers
CID: 190630
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

file reworked, not valid anymore and marked fixed.


Fix crash when serializing empty delegates in C#

Resolves #67212

The rebase went wrong, you seem to have squashed your commits together with a previously merged commit. You might be able to fix it by resetting Tina previous version using git reflog, and then rebase on upstream master.
See PR workflow for tips: https://docs.godotengine.org/en/latest/community/contributing/pr_workflow.html#the-interactive-rebase

Ok finally I got it :D sorry @akien-mga for the messed up history :D
Not that familiar with the rebasing approach yet.

Thanks! And congrats for your first merged Godot contribution :tada:


chore(master): release 1.0.0

:robot: I have created a release beep boop
1.0.0 (2023-08-08)
Features

initial commit (45929d5)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/laravel-stripe-webhooks/releases/tag/v1.0.0 :sunflower:


Microsoft Edge not support

Will Microsoft Edge browser support be added soon?

What is Edge's user agent?

Microsoft Edge:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.
Windows 10 Mobile:
Mozilla/5.0 (Windows Phone 10.0; Android 4.2.1; DEVICE INFO) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Mobile Safari/537.36 Edge/12.
Source: https://msdn.microsoft.com/en-us/library/hh869301(v=vs.85).aspx


Library request in CDNJS

Hi!
I am a member of CDNJS. There is a library request cdnjs/cdnjs#10616.
I am in charging of adding this library, and I want confirm which files should I add to CDNJS.
Could you tell me if all files under build should be added? Or we need other files?
Thanks!

Yes, only the files under build need to be added. Thanks!

/ping @extend1994


Nukies issue

Description

The shuttle and the mobs spawned, but it didn't grabbed the players, we had to ghost role them.
The shuttle needs to be changed to infiltrator
The shuttle spawned too far away to be picked up by mass scanner
Nukies need their own access ID and doors
Reproduction

Screenshots

Additional context

Nuke detection needs to be more robust i.e. right now it only checks for detonation. Should check if it's detonated within the area of the correct station.
Also needs minor / major victory I think.

could we make it an antag opt in role so it can grab players like it normally does for round start syndies

Also needs minor / major victory I think.

I would also like to see the old humiliating defeats such as when it's detonated on a Syndicate base(just the shuttle for now).

shuttle does get spawned pretty far but it might be helpful for a syndi shuttle console with a 512x512 range instead of 256

Syndie shuttle now has 500 range I'm sure.
Nukies are opt in.
Seems to work but idk about access


Docker swarm/mesh routing

Thank you for the useful information. I have a question about docker swarm using ingress network "Mesh Routing" in order for me to make mesh routing work i installed two windows server 2016 version 1709 my manager node is on one server and worker node on another server i ran the init command to join one node to my docker swarm manager and i deployed one image on one of the node and created 2 replicas i see one replica running on worker node/Server1 and the other on node manager/Server2 which mean it's working as expected and i can access one application thru both servers. But when my Server1 get restarted my Manager node has lost the communication with the worker node even if the server1 is up again and when i run the container ls i don't see any container running on my worker node/Server1 the swarm manager does it's job now both the replicas are running on the other server2/Manager node until otherwise i explicitly scale the service on the manager node than the  worker node can see the new containers and it's accessible. But my question is why worker node is not coming live after it's restarted? Do i have to keep scaling my services on manager node in order to see the services on worker nodes after i restart the servers each time? I'm sure there is a way to fix this issue but i'm not able to figure it out please share your ideas on how to solve this issue.

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

ID: 16eeefcb-95dc-952a-18b9-2c00d190a995
Version Independent ID: 5becd139-9e1d-4e41-04a4-9c96cf8f9f72
Content: Getting Started with Swarm Mode
Content Source: virtualization/windowscontainers/manage-containers/swarm-mode.md
Service: windows-containers
Product: windows-containers
GitHub Login: @kallie-b

We can create services but with randoms ports, we need to define a range of ports and deploy it in order.
We need to create a service with replicas in a range of ports (8081 - 8084) for example, --publish mode=host,target=80 but we need to define a range like: --replicas 4 --publish mode=host,target=80,publish=8081,8082,8083,8084 or 8081-8084

I think it would be acceptable to use the dnsrr  until the mesh work is finished, but i would really appreciate to get an working example anywhere in the docs with an compose file and stack deploy like an real world application... It´s not very easy to get swarm windows examples.

i figured it out. it worked with an external network and host mode port. Be careful about the "Tips & Insights" section . I deleted the standard overlay network and created an own overlay network.
If you use a compose file and swarm stack deploy you can specify the mode in the file with:
    ports:       - target: 80         published: 62xxx         protocol: tcp         mode: host     networks:        - mycreatednetwork     deploy:       mode: replicated       replicas: 1       endpoint_mode: dnsrr

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Fixed folder in manual method

Hello thanks for the great project!
I noticed that the folder is not <IP_ADDRESS> since a long time. As of version 4.1, this is <IP_ADDRESS>

Closing, it is out of date and doesn't really look like this will get merged any time soon anyway.


Partial wildcard matching

My team leverages a few fields in our headers for authentication.  Namely
x-api-key, x-api-secret, and x-api-password
Currently, we can redact all of those by providing the three individual strings to pino, but I was wondering if there's a way we could use the wildcard character to pass pino something like req.headers["x-api-*"] instead?

pino-noir is deprecated, please use the react functionality in pino itself.
This is not possible right now anyway.


Code : Search in Tries

📚 Documentation
Implement the function SearchWord for the Trie class.
For a Trie, write the function for searching a word. Return true if the word is found successfully, otherwise return false.
Have you read the Contributing Guidelines on Pull Requests?
Yes

/assign


Bug report: running exp_sarsa_1

epoch: 45	average reward: -0.87	latest average reward: -1.10
Evaluation environment...
Evaluation reward for sarsa: -1.90
100%|██████████| 10/10 [00:00<00:00, 434.39it/s]
78it [00:00, 87.76it/s]
Traceback (most recent call last):
File "D:/projects/PyMatch/research_master/train_learner.py", line 25, in
learner.fit(**params['fit'])
File "D:\projects\PyMatch\pymatch\DeepLearning\learner.py", line 184, in fit
train_loss = self.fit_epoch(device)
File "D:\projects\PyMatch\pymatch\ReinforcementLearning\learner.py", line 520, in fit_epoch
target[mask] = (1 - self.alpha) * target[mask] + self.alpha * (
IndexError: The shape of the mask [64, 1] at index 1 does not match the shape of the indexed tensor [64, 2] at index 1

This seems to be random... sometimes it happens sometimes it doesnt....

Simply happens due to the one_hot_encoding which is buggy


Issue with SubgraphLoader() and/or Torch

Hi, I obtained this error by just running the first example train_gcn.py
Traceback (most recent call last):
File "/home/ersa/spage2vec/pyg_autoscale/examples/train_gcn.py", line 85, in
train(model, loader, optimizer)
File "/home/ersa/spage2vec/pyg_autoscale/examples/train_gcn.py", line 57, in train
for batch, *args in loader:
File "/home/ersa/miniconda3/envs/spage2vec/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 633, in next
data = self._next_data()
File "/home/ersa/miniconda3/envs/spage2vec/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 677, in _next_data
data = self._dataset_fetcher.fetch(index)  # may raise StopIteration
File "/home/ersa/miniconda3/envs/spage2vec/lib/python3.10/site-packages/torch/utils/data/_utils/fetch.py", line 54, in fetch
return self.collate_fn(data)
File "/home/ersa/miniconda3/envs/spage2vec/lib/python3.10/site-packages/torch_geometric_autoscale/loader.py", line 74, in compute_subgraph
rowptr, col, value, n_id = relabel_fn(rowptr, col, value, n_id,
File "/home/ersa/miniconda3/envs/spage2vec/lib/python3.10/site-packages/torch/_ops.py", line 502, in call
return self._op(*args, **kwargs or {})
RuntimeError: isBool() INTERNAL ASSERT FAILED at "/home/ersa/miniconda3/envs/spage2vec/lib/python3.10/site-packages/torch/include/ATen/core/ivalue.h":666, please report a bug to PyTorch.
My conda environment:
python version==3.10.13.final.0
torch                     1.13.1+cu117             pypi_0    pypi
torch-cluster             1.6.3+pt20cu117          pypi_0    pypi
torch-geometric           2.4.0                    pypi_0    pypi
torch-geometric-autoscale 0.0.0                    pypi_0    pypi
torch-scatter             2.1.2+pt20cu117          pypi_0    pypi
torch-sparse              0.6.18+pt20cu117          pypi_0    pypi

Thanks for reporting. What does
import torch
import torch_geometric_autoscale
relabel_fn = torch.ops.torch_geometric_autoscale.relabel_one_hop

rowptr = torch.tensor([0, 2, 3])
col = torch.tensor([0, 1, 0])
value = torch.tensor([0, 1, 2])
n_id = torch.tensor([0, 1])

relabel_fn(rowptr, col, value, n_id, True)
relabel_fn(rowptr, col, value, n_id, False)

return for you?

It returned this:
File "/home/ersa/spage2vec/trial_run/troubleshoot.py", line 10, in
relabel_fn(rowptr, col, value, n_id, True)
File "/home/ersa/miniconda3/envs/spage2vec/lib/python3.10/site-packages/torch/_ops.py", line 502, in call
return self._op(*args, **kwargs or {})
RuntimeError: isBool() INTERNAL ASSERT FAILED at "/home/ersa/miniconda3/envs/spage2vec/lib/python3.10/site-packages/torch/include/ATen/core/ivalue.h":666, please report a bug to PyTorch.

Can you show me the installation log when running python setup.py install? Looks like something went wrong during installation.

I accidentally deleted my conda environment, but was able to install it correctly with stable CUDA/Torch combination. Thanks for the help!

I had installed an unstable version combination of CUDA and Torch and was fix restarting my conda environment. Thanks for the help!


Update to newest version of CloudPickle.

Addresses #23119 for next release.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @ryanthompson591 or @Abacn

retest this please

retest this please

retest this please


Delay and busy-waiting

I was looking to improve the Delay struct used for busy-waiting when waiting for the card to do some work.
I wanted to discuss:

How we can improve the current Delay which acts more like a Retry counter than a delay.
Rely on embedded-hal crates for the delay waiting instead of reading from volatile:

support the embedded-hal (0.2) timer::CountDown
support the embedded-hal (1.0.0-alpha.10) delay::DelayUs
support the embedded-hal-async delay::DelayUs

This issue is also part of my efforts to improve speed, reliability and introduce async interface in this upstream repo.
Also related to #80

I added a change which uses the blocking DelayUs trait.
Really we just need something that slows down the retries so the card isn't battered while calculating its response, and ideally something independent if transfer clock speed.


Jump to table/data buttons do not show up in safari

In Safari, the buttons to jump to specific elements of the page do not show up.

I don't see buttons to jump to elements on any browser. The return to top button is on the home page in every browser and functions.
Browsers check: Safari, and google.