Remove hard requirement for hypernetx.

The requirement on HyperNetX is not hard and is problematic, as it is not compatible with NetworkX 3, which is more than a year old. With this pull request, users that do not use hypergraphs are free to use NetworkX 3, while others must stay on NetworkX 2 (as transient dependency due to HyperNetX).
We exclusively use HyperNetX in places where we transform user-provided hypergraph instances into complex classes or vice versa. Such code points are only ever called when the user itself interacts with HyperNetX and thus did install it themself. We don't need to force that dependency.

For why the hard dependency on HyperNetX and its incompatibility with NetworkX 3 is problematic, see e.g. here: https://github.com/pyt-team/TopoEmbedX/issues/39#issuecomment-1906217924. It now forces us to stay with older versions of SciPy as well.


how to control the index from another widget?

I want to add a slider which can control the index of the card. Can you please help me with that??

You can't directly change index after render. But by using async example you can rerender with given list of data.
So at start you have a list with length of 10, and you want to show third item. You can remove items at index 1 and 2 and you only left with list which starts at third item. So all we need to do is get a sublist from index to length of original list.
For example
List<dynamic> list;

// for going given index
void changeIndex(int index) {
    _streamController.add(list.sublist(index, list.length));
}


Missing WinStoreAppLinks folder

On point 6 of the instructions there is no "WinStoreAppLinks" folder within the zip file here: https://github.com/rickstaa/Todoist_Global_Shortcuts_WIN10/archive/master.zip

Dear Filcole,
I'm sorry for the inconvenience I fixed the issue. If you download the zip again, it now includes the folder. Can you maybe check if the install process is working?
Can you maybe keep me posted on if it is working? I'm unsure if the shortcut to Todoist in the WinStoreAppLinks will work on other peoples PCS. Otherwise, I have to create a small installer or update the README file.
In the meantime the shortcut didn't work here is what you should do to get the script working.

As it is tough to open WinStoreApps by coding you need to create a "WinStoreAppLinks" folder in your "Program Files" folder.
Open this folder in Finder.
Press the start key.
Drag the Todoist Icon to the "WinStoreAppLinks" folder this will create the shortcut I use to launch the program.

Greetings,
Thanks in advance,
Rick Staa,

I created an installer hope that helps ;).

Dear Filcole,
I'm sorry for the inconvenience I fixed the issue. I just uploaded the new version. In this version, there is an installer. In the readme, you can find how to install the script.
Greetings,
Thanks in advance,
Rick Staa,


Add support for several model files per benchmark

Currently a backend can only specify one model file for a benchmark.
Future backends may use models that are defined in several files. Specifically I'm aware that there are models that need 2 files.
I see 2 possible solutions here:

Add a new setting to the protobuf config. We can make it optional so we don't have to update our current backends. We will only support fixed number of files.
Use CustomSetting field in the benchmark settings. We can add special handling of some CustomSetting fields to the app frontend to download files using provided URLs.

Per our discussion, a model archive file (say, foo.zip) should work. Leave op after we test it.

Downloading a zip file and opening within interface function works.


Memory usage w/ multiple Clappr Players (HLS)

Browser: Chrome 58.0.3029.110
OS: Windows 10 v1703
Clappr Version: 0.2.27
Hi guys,
I've been currently using Clappr to build a video wall, in which will be displayed CCTV streams in HLS format. There will be at maximum 9 streams displayed, which may come from the same source or from a different one.
My problem is that apparently having 9 displayed streams is eating all browser memory, reaching > 1.5GB over time, slowing down the performance of the site and ultimately causing it to crash. I've tried to use the maxBufferLength property, setting it to 5 seconds, but I've had no luck in solving the problem so far.
Can anyone provide any feedback regarding a possible solution?
Thanks.

@andrefilipegsilva you may consider directly using hls.js library for this project handling your 9 html5 video elements to reduce as much as possible the memory requirements ?

@kslimani It's possible but I've adapted my code to work with Clappr...
I'm hoping for a solution within Clappr but if there isn't any, I will follow your suggestion...

@andrefilipegsilva I'd encourage you to review the hls.js config options very carefully.  maxBufferLength/maxBufferSize are more of suggestions than real limits.  You can use maxMaxBufferLength if necessary to cap.
You might also try to limit the resolution/bitrate of each by specifying the currentLevel of the hls.js playback if each rendered stream in your grid is smaller (capLevelToPlayerSize is a more algorithmic approach to this same thing).
In reality though, 1.5GB is (sadly) pretty reasonable to play back 9 streams at the same time in Chrome.  Did you think about (a) using Edge to play back hls natively or (b) increasing the memory on the computer?

How did you set maxBufferLength @andrefilipegsilva  ?

@bikegriffith The thing is that it only reaches such amount of memory usage over time, i.e. 5-10-15 minutes. It is mandatory that my project runs across different browsers, so Edge alone is not an option. Increasing memory is a possibility but I'm trying to solve this issue in a programmatic way rather than in a physical one.
I'm gonna try to use the flags you specified and then I'll share the results.
@leandromoreira I've set the flag either like this:
self.player = new Clappr.Player({
            source: self.hlsAddress(),
            poster: 'http://clappr.io/poster.png',
            mute: true,
            width: '100%',
            height: '100%',
            disableKeyboardShortcuts: true,
            hideVolumeBar: true,
            maxBufferLength: 5,
            hlsjsConfig: {
                maxBufferLength: 5
            }

@andrefilipegsilva You need to nest hlsjsConfig inside a playback dictionary, e.g.:
self.player = new Clappr.Player({
            source: self.hlsAddress(),
            poster: 'http://clappr.io/poster.png',
            mute: true,
            width: '100%',
            height: '100%',
            disableKeyboardShortcuts: true,
            hideVolumeBar: true,
            playback: {
                hlsjsConfig: {
                    maxBufferLength: 5
                }
            }

@bikegriffith I've set the hlsjsConfig debug property to true without nesting the hlsjsConfig inside the playback and it worked... Is it different for the maxBufferLength property?

@andrefilipegsilva it worked because of "legacy" reason.
For consistency, i recommend using
playback: {hlsjsConfig:{ /* hls.js constructor options here */ }}

like @bikegriffith suggested.
(For more details, see this part of HLS playback)

BTW, i see lot of people which require to customize hls.js instance with Clappr player. Maybe it would be a nice feature to introduce, for example, an advanced "before attach media" playback event which allow developer to manipulate hls instance before call attachMedia method ?

Even while setting correctly the hlsjsConfig dictionary within the playback with the options maxBufferLength: 5 and maxMaxBufferLength: 5 it escalates to over 1.5 GB. Any other ideas? I'm kinda stuck...

@andrefilipegsilva maybe you could attempt to either use .mp4 sources or directly test with hls.js to determine if the memory (possible leak ?) comes from Clappr or from hls.js. (because if memory issues comes from Clappr then tuning hls.js will change nothing, or the inverse will point us to the right direction for additional help)

I'm gonna switch to 'pure' hls.js and I'll come back with results.
Thanks!

I've implemented pure hls.js and the results were better (as expected because there's no additional overhead), but the memory still rises overtime (around 15-20 minutes of spectating) to ~ 1GB and up, and it doesn't stop nor decrease significantly.
I've configured HLS with these parameters:
var config = {
            capLevelToPlayerSize: true,
            maxBufferSize: 30,
            maxBufferLength: 5
        };
        self.hls = new Hls(config);

If you think this is somewhat unrelated to this project I can also ask this question on hls.js forum...
Thanks,

Well it seems there is several issues open at hls.js about memory leak, but it is hard to say if it is related to your problem.
Debug such issue may be hard. One opened issue suggest to use this technic to spot the problem. Maybe you could have a try and attempt report to hls.js repository.

It's likely to be something on hls.js based on your tests, so I'll label this as wontfix. Thanks


[WIP] Make it easier to mount known_hosts from a ConfigMap

Addresses #1113, and helps with #1101 by making the chart usable from the integration test (I think).
WIP until I've actually tried the Helm chart install myself.

Note to self, this may need to alter the howto bit of setup.md, and possibly FAQ.

@squaremo you could also bump Flux version to 1.4.0

PR for the first bit is #1154.


App doesn't work in Internet Explorer

Add a banner like that for small screens, but that tells the user that their browser is out of date and to switch to a new browser.

This is what it looks like in IE:

no requirements tree
tutorial doesn't work
can search for courses, but cannot drag them into the schedule
course x buttons are out of place
text on login button on home screen runs out of the button

To be clear, the best solution is probably not to add support for IE, but rather to alert users to the problem so that they can switch browsers.


Combiling partial ids while loading data

Coverage decreased (-0.3%) to 94.18% when pulling ac06f897dad18f85b0f39b8ae6f299cc28c4ef7e on fix/process-partial-ids into f5f6f31938f03c8844d6e87b36423f5783df2fea on master.


[Bug]: ABSL_FLAG(std::string) does not accept std::string_view as a default value

Describe the issue
When defining a flag of std::string type, the default value must be an std::string or const char*. It would be great if std::string_view were also accepted.
Following Google conventions, I frequently have string constants in the form:
constexpr std::string_view kMyStringConstant = "asdf";

which I tend to prefer over constexpr const char* because std::string_view has a constexpr constructor that allows explicit zeroes in strings.
Steps to reproduce the problem
The following does not compile:
constexpr std::string_view kMyStringConstant = "asdf";

ABSL_FLAG(std::string, my_flag_name, kMyStringConstant, "my message");

Of course, I can work around this with:
ABSL_FLAG(std::string, my_flag_name, std::string(kMyStringConstant), "my message");

What version of Abseil are you using?
Pinned to commit 74eee2aff683cc7dcd2dbaa69b2c654596d8024e
What operating system and version are you using?
MacOS Ventura 13.5.2
What compiler and version are you using?
$ clang -v
Apple clang version 14.0.3 (clang-14<IP_ADDRESS>.1)
Target: arm64-apple-darwin22.6.0
Thread model: posix
InstalledDir: /Applications/Xcode_14.3.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

What build system are you using?
bazel 6.1.1
Additional context
No response

If someone comes up with a patch to this that doesn't break existing code, then I will consider accepting it, but as you said, the workaround is so trivial that I don't think anyone is going to spend time looking into this.


docs: Issue in page Build an IoT App with Go - add links to Go Driver and Scylla U go session

I would like to report an issue in page https://iot.scylladb.com/master/build-with-go
It would be usefull to add links to

the relevant Driver
the relevant Scylla U course https://university.scylladb.com/courses/using-scylla-drivers/lessons/golang-and-scylla-part-1/

The sames goes for all drivers


Inject the service manager here to prevent the latest zend-mvc from throwing deprecation notices

AbstractPluginManager that don't have the SL injected cause panic with the latest zend-servicemanager release. See \Zend\Mvc\Service\ServiceManagerConfig
// For service locator aware plugin managers that do not have
                // the service locator already injected, inject it, but emit a
                // deprecation notice.
                if ($instance instanceof ServiceLocatorAwareInterface
                    && $instance instanceof AbstractPluginManager
                    && ! $instance->getServiceLocator()
                ) {
                    trigger_error(sprintf(
                        'ServiceLocatorAwareInterface is deprecated and will be removed in version 3.0, along '
                        . 'with the ServiceLocatorAwareInitializer. Please update your %s plugin manager factory '
                        . 'to inject the parent service locator via the constructor.',
                        get_class($instance)
                    ), E_USER_DEPRECATED);
                    $instance->setServiceLocator($container);
                }

Going to merge this. I haven't done any PHP works in months so if there's someone that wants to step up as a maintainer let's make that happen.

@spiffyjr if you merged it, why the problem persists? Thanks

@spiffyjr if can't create a new release with the this PR, I can do for you

@pensiero you can use my fork, it has this changes and works with zf2 and zf3. https://packagist.org/packages/kokspflanze/zfc-twig in version 1.3.0

Thanks @kokspflanze


CUDA out of memory problem

Thanks for your nice work. When evaluating HOTR on vcoco dataset (vcoco_multi_train) on a server with 8 GeForce RTX 2080Ti Cards, I encountered the CUDA out of memory problem.

File "/project/HOI/HOTR-main/hotr/engine/evaluator_vcoco.py", line 53, in vcoco_evaluate
gather_res = utils.all_gather(res)
File "/project/HOI/HOTR-main/hotr/util/misc.py", line 129, in all_gather
data_list.append(pickle.loads(buffer))
File "/anaconda3/envs/kakaobrain/lib/python3.7/site-packages/torch/storage.py", line 141, in _load_from_bytes
return torch.load(io.BytesIO(b))
File "/anaconda3/envs/kakaobrain/lib/python3.7/site-packages/torch/serialization.py", line 595, in load
return _legacy_load(opened_file, map_location, pickle_module, **pickle_load_args)
File "/anaconda3/envs/kakaobrain/lib/python3.7/site-packages/torch/serialization.py", line 774, in _legacy_load
result = unpickler.load()
File "/anaconda3/envs/kakaobrain/lib/python3.7/site-packages/torch/serialization.py", line 730, in persistent_load
deserialized_objects[root_key] = restore_location(obj, location)
File "/anaconda3/envs/kakaobrain/lib/python3.7/site-packages/torch/serialization.py", line 175, in default_restore_location
result = fn(storage, location)
File "/anaconda3/envs/kakaobrain/lib/python3.7/site-packages/torch/serialization.py", line 155, in _cuda_deserialize
return storage_type(obj.size())
File "/anaconda3/envs/kakaobrain/lib/python3.7/site-packages/torch/cuda/init.py", line 462, in _lazy_new
return super(_CudaBase, cls).new(cls, *args, **kwargs)
RuntimeError: CUDA error: out of memory

This problem seems happens on line 53 of evaluator_vcoco.py, utils.all_gather(res) . Any suggestions how to solve this problem? Thanks a lot.

This happens because the model was based on 8 cards of 32G Titan V100 with a batch size 2.
(to my recall, GTX 2080Ti has an 11G memory)
You can either cut down the batch size to 1 or perform a smaller augmentation for the input size of the image (permalink below).
https://github.com/kakaobrain/HOTR/blob/a2e19511d6131220f430ba2d76a95a03a0f7556e/hotr/data/datasets/vcoco.py#L440
Although this might make the model run, note that both will harm the original performance of the model.

I meet the same problem with RTX 2080ti. I change some code in /util/misc.py to solve it:
#line127
for size, tensor in zip(size_list, tensor_list):
torch.cuda.empty_cache() # add empty_cache to solve it!
buffer = tensor.cpu().numpy().tobytes()[:size]
data_list.append(pickle.loads(buffer))


'ef migrations remove' uses designer files to walkback migrations

Brief Description
dotnet ef migrations remove uses the migration *.Designer.cs file to rollback state of the DbContextModelSnapshot.cs file.
This is likely to cause problems when merging changes across multiple branches.

Steps to reproduce
To reproduce the issue, clone this repository and run: dotnet ef migrations remove
Please see the readme for full documentation
If this is the intended result, I would be very interested to hear how others are managing changes across multiple branches.

Further technical details
EF Core version: 1.1.2
Database Provider: Npgsql.EntityFrameworkCore.PostgreSQL
Operating system: Mac
IDE: VS Code

@bricelam to look into workarounds for 2.0.

This is another manifestation of the root cause of issue #996. Having #1911 would help us detect this situation and handle it better.
Workaround
In this situation, you should be able to use the following workflow.

Delete<PHONE_NUMBER>2356_modelC.cs and<PHONE_NUMBER>2356_modelC.Designer.cs
Run Remove-Migration (or dotnet ef migrations remove)

A manual deletion is detected
The snapshot from modelB is used

Run Add-Migration to re-add the changes in the current branch

@bricelam thanks for the suggestion. I can see that it should work fine if the issues are caught quickly. Unfortunately, this doesn't help much, since it still requires developers to:

be aware of the issue
check that there weren't any new migrations (even though there may not be any conflicts) before merging  their PRs
regenerate and re-validate their existing migration

Not to mention the mess this can cause downstream if the issues are not caught right away. Trying to sort through designer files to identify the source of the issues can be quite time consuming.
Can you confirm that the designer file is not used when generating migrations? And that it will only become a problem when trying to roll them back?

Can you confirm that the designer file is not used when generating migrations? And that it will only become a problem when trying to roll them back?

Correct. The model snapshot is used to generate new migrations, and it will get merged properly like any other version controlled file.
The issue here is we need to synthesize the previous model snapshot which gets messy if you've merge new migrations into the mix.
As part of using Migrations, I think developers need to be very aware of when they merge new migrations into a branch. Being able to detect when a merge occurred (issue #1911) would go a long way to prevent errors that may otherwise go undetected. Heck, a dotnet ef migrations rebase command could even be made to simplify the process.

That makes sense. My expectation was that dotnet ef migrations remove would have used the last defined migration's (based on timestamp) Down method to rollback the model snapshot.

It's been a little while on this and I know you all are very busy but I was wondering if there was any update on the design. I would love to contribute if there is room. But moreover I think it would be beneficial if the design discussion was open to the community for input. If this is already the case, can you point me to where this is?

@jaredcnance We haven't been working directly on this at the moment. However, we'll have a discussion (probably not for a couple of weeks) and see if we can put some ideas together. Any ideas you have are most welcome.

@ajcvickers thanks for the update. My main concerns revolve around the use/need for incremental snapshots. There should be enough information in the current snapshot and migration definitions to handle forward and backward migrations. The ideal case would be to have a migration API that defined bi-directional operations so a developer only has to define the up migration. But, in lieu of that, the down method can be used to rollback a migration. Migrations should ALWAYS be treated as serial operations and as such shouldn't need any special merge tooling or incremental snapshots. Some of the best prior art from a developer experience, in my opinion, that does this includes Active Record and Ecto.
While I'm not familiar with EntityFrameworkCore's internal architecture, I'd love to do more research on how this can be achieved if there is agreement from the EF team.
Again, thanks for all the hard work you guys are doing, I don't feel like you guys get enough love!

Moved this temporarily into 2.1 milestone so that @bricelam can write down some thoughts.


close method

A close method, finishing the execution of the store and releasing all the resources being used, must be implemented.

Close methods are available.


Document lsst_specs.py

This includes further docs for lsst_specs.py, as requested in the Code Review.

I addressed the comments. This PR addresses one of the comments from Mike requesting further docs for a function here. But I improved the docs in general for this file.


Add LangChain webinar notebooks from Akmal

Can you add some documentation in the notebook cells themselves to explain the steps? Also, the notebook names could be better. The names don't give any indication of what is being demonstrated in them.

Not "in" the cells, but add markdown cells above the code cells to explain what's going on.


json file in /assets cannot be imported using useStorage().getItem() within server function

Environment
Operating System: Darwin
Node Version: v18.16.0
Nuxt Version: 3.6.2
Nitro Version: 2.5.2
Package Manager<EMAIL_ADDRESS>Builder: vite
User Config: app, runtimeConfig, components, css, plugins, buildModules, modules, colorMode, supabase, target, build
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules: -
Reproduction
Very simple, so hopefully not needed!
Describe the bug
I'm trying to import a JSON file located at /assets/test.json within a serverless function located at /server/test.js
The function code is:
export default defineEventHandler(async (event) => {
    const test = await useStorage().getItem(`assets/server/test.json`);

    return {
       statusCode: 200,
       body: JSON.stringify(test),
  };
}

However, it says that the file cannot be found and test returns null.
Is it in the wrong directory?
Additional context
No response
Logs
No response

Try using the public directory instead.

Since you are using "Nuxt", you should put (server) assets inside server/assets/test.json in order to make it accessible.
(sorry for confusion. we probably need to make it more clear about Nuxt usage)

Since you are using "Nuxt", you should put (server) assets inside server/assets/test.json in order to make it accessible.
(sorry for confusion. we probably need to make it more clear about Nuxt usage)

Putting them in /server/assets worked!
But I'm very confused by this: putting an asset in/server/assets/test.json allows you to import it using await useStorage().getItem('assets/server/phrases.json') ?
The directories switch places?


Cannot wire RegularFileProperties using Provider.map()

Current Behavior
When I try to wire two RegularFileProperties together using map(), I get an error message stating that they are incompatible:

Cannot get the value of task ':consume' property 'input' of type org.gradle.api.file.RegularFile as the provider associated with this property returned a value of type org.gradle.api.internal.file.DefaultFilePropertyFactory$DefaultRegularFileVar.

The task have an OutputFile and an InputFile property respectively:
abstract class ProducerTask extends DefaultTask {
    @OutputFile
    abstract RegularFileProperty getOutput()
}

abstract class ConsumerTask extends DefaultTask {
    @InputFile
    abstract RegularFileProperty getInput()
}

I'm using register() to create the tasks:
def produce = tasks.register('produce', ProducerTask) {
    output = file(new File(buildDir, 'some_file'))
}
def consume = tasks.register('consume', ConsumerTask) {
    input = produce.map { it.output }
}

Expected Behavior
My expectation would be that it's possible to wire the two properties like this.
Context (optional)
No response
Steps to Reproduce
The following build.gradle reproduces the issue:
abstract class ProducerTask extends DefaultTask {
    @OutputFile
    abstract RegularFileProperty getOutput()

    @TaskAction
    void produce() {
        output.get().getAsFile().text = 'produced'
    }
}

abstract class ConsumerTask extends DefaultTask {
    @InputFile
    abstract RegularFileProperty getInput()

    @TaskAction
    void produce() {
        println "Consuming: ${input.ge().getAsFile().text}"
    }
}

def produce = tasks.register('produce', ProducerTask) {
    output = file(new File(buildDir, 'some_file'))
}
def consume = tasks.register('consume', ConsumerTask) {
    input = produce.map { it.output }
}

Just call the consume task.
Gradle version
7.5.1, 8.3
Build scan URL (optional)
No response
Your Environment (optional)
No response

I've thought a bit about this. Is the user supposed to do the following to wire:
def consume = tasks.register('consume', ConsumerTask) {
    input = produce.map { it.output.get().getRegularFile() }
}

I'm actually debugging a different bigger issue and got confused with how to properly wire properties together using map(). I'm guessing input = produce.map { it.output.get() } is the way to go.

produce.map { it.output } returns Provider<RegularFileProperty>, but you don't want to wrap a RegularFileProperty in a Provider. To solve that you should use flatMap, e.g.:
input = produce.flatMao { it.output }.

@asodja Actually, one more question if I may. I get that the two forms are equivalent when it comes to what gets returned. Do both forms (the map() form I showed and the flatMap() form that you showed) behave the same when it comes to preserving task relationships?

They should both carry task dependencies in that case, yes.
There is small difference in execution though, and I've seen some issues where task relationship get "lost" with .map { it.something.get() } with chaining, e.g.: https://github.com/gradle/gradle/issues/26363#issuecomment-1717733649.
Although that might be also Gradle bug.

FTR, we are considering supporting (via generated Kotlin extension methods, and some Groovy magic) a notation where you could write the above as:
input = produce.output

See https://github.com/gradle/gradle/issues/25755


Add discriminability

A function for computing the discriminability from a distance matrix and a set of associated labels. Reference: Eric W. Bridgeford, et al. "Optimal Decisions for Reference Pipelines and Datasets: Applications in Connectomics." Bioarxiv (2019).


Nvidia Quadra K1200 drivers install, but the device does not use the updated driver

With Windows 10 1909, I have noticed that for some reason unknown to me, the drivers for the Nvidia display adapter do install, but then ARENT USED.  The device continues to use the previous driver version.
Any ideas why this could be taking place?

Using version 3.0.5 by the way.

-URI "http://serverConfigMgrWebService/ConfigMgr.asmx" -SecretKey "secret" -Filter "Drivers" -DeploymentType "DriverUpdate" -TargetOSVersion 18363


WSL filesystem keeps accumulating corrupted file and directory entries

Windows Version
Microsoft Windows [Version 10.0.19045.4170]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-microsoft-standard-WSL2
Distro Version
Ubuntu 22.04.2
Other Software
Visual Studio Code:
Version: 1.87.2 (user setup)
Electron: 27.3.2
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045
Repro Steps
Attempt to delete file in WSL2 after having opened folder directory in VSCode, run said project, some files get corrupted, attempt to delete corrupted files, file manager then claims they no longer exist in that location. See files in file manager, attempt to delete again, get error.
Expected Behavior
The files should delete.
Actual Behavior

Related Issues
https://github.com/microsoft/WSL/issues/1662

/logs

There's no logs available, as the process was done through a file manager not the terminal.

@OneBlue is looking into this.


Added proxy tests referring:

https://github.com/mcollina/node-coap/issues/55
https://github.com/mcollina/node-coap/issues/56

Can you please format the tests so that they follows the structure of the of the others? So they will be picked by travis, too!

Maybe this PR is not needed anymore, or maybe it can be added in an examples folder. I've already created a small test that covers #55 and I'm in process of doing the same with #56.

Thanks Daniel!
So do you think that it adds any value if I add my tests to the examples folder?

It's a good question, I don't know what Matteo thinks about this: should we give as much examples as possible or should we give just small examples one per feature? I think the most interesting thing about the example was to show the bugs themselves, and that functionality is already exposed in the tests, but I prefer to listen to Matteo's opinion on the subject.

I think it's ok to have some integration tests, added to ensure bugs like
this one. Let's put them in a folder like 'test/integration', so we know
what we are talking about.
Il giorno lun 25 mag 2015 alle 15:16 Daniel Moran<EMAIL_ADDRESS>ha scritto:

It's a good question, I don't know what Matteo thinks about this: should
we give as much examples as possible or should we give just small examples
one per feature? I think the most interesting thing about the example was
to show the bugs themselves, and that functionality is already exposed in
the tests, but I prefer to listen to Matteo's opinion on the subject.
—
Reply to this email directly or view it on GitHub
https://github.com/mcollina/node-coap/pull/59#issuecomment-105230199.

Just to make sure that there is no misunderstanding. I create a subfolder under 'test' (or 'exampels'?) called 'integration' and under that folder with my tests called 'ProxyTests'?

why not just putting them in 'test/integration'?
Il giorno mar 26 mag 2015 alle 11:23 Claes Nilsson<EMAIL_ADDRESS>ha scritto:

Just to make sure that there is no misunderstanding. I create a subfolder
under 'test' (or 'exampels'?) called 'integration' and under that folder
with my tests called 'ProxyTests'?
—
Reply to this email directly or view it on GitHub
https://github.com/mcollina/node-coap/pull/59#issuecomment-105461625.


clinic doctor issues running worker thread test

Attempting to run the following in Node.js 13.11.0
const {
  Worker,
  isMainThread,
} = require('worker_threads');

if (isMainThread) {

  for (let n = 0; n < 100; n++) {
    new Worker(__filename);
  }

} else {

  const m = [...new Array(1000)];
  JSON.stringify(m);

}

Any number of threads causes the same failure. See gist: https://gist.github.com/jasnell/a8e584452e5ac4da6a1f8b6f90e8bf28
Using clinic v5.0.0 (clinic doctor -- node t.js)
Error:
To generate the report press: Ctrl + C
[    ] Analysing dataundefined:20
      if (!found0 || !found1 || !found2 || !found3 || !found4) throw new Error("Decoded message is not valid")
                                                               ^

Error: Decoded message is not valid
    at Object.decode (eval at line.toFunction (/home/james/.nvm/versions/node/v13.11.0/lib/node_modules/clinic/node_modules/generate-function/index.js:172:21), <anonymous>:20:70)
    at ProcessStatDecoder._transform (/home/james/.nvm/versions/node/v13.11.0/lib/node_modules/clinic/node_modules/@nearform/doctor/format/abstract-decoder.js:42:31)
    at ProcessStatDecoder.Transform._read (_stream_transform.js:191:10)
    at ProcessStatDecoder.Transform._write (_stream_transform.js:179:12)
    at doWrite (_stream_writable.js:392:12)
    at writeOrBuffer (_stream_writable.js:374:5)
    at ProcessStatDecoder.Writable.write (_stream_writable.js:314:12)
    at ReadStream.ondata (_stream_readable.js:708:22)
    at ReadStream.emit (events.js:315:20)
    at addChunk (_stream_readable.js:297:12)

The issue appears to have been introduced between Node.js 13.9.0 and Node.js 13.10.0. With 13.9.0 no error is thrown.

The issue appears to be a race condition for worker threads... essentially, every worker has it's own copy of the sampler code which ends up concurrently writing samples into the same file causing it to be corrupted. The fix should be to redirect worker thread samples into their own files, which we can then process separately.
Refs: https://github.com/nearform/node-clinic-common/pull/22


Conversion of Binary Number to Decimal Number in C++

💥 Proposal
(A clear and concise description of what the proposal is.)
Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
Hey I am GSSOC'21 Participant and I have read the Contributing Guidelines.
I want to propose a program in which Binary Number (up to 10 digits) will be given as input and in output we get the number in its Decimal form.
Example: Input  1000   Output  8
@ankitaggarwal23 Please assign me this issue.

Hey I am GSSOC'21 Participant ,
I want to write a program:
input: Binary Number
output:  we get the number in its Decimal form.
Example: Input 1000 Output 8
@ankitaggarwal23 Please assign me this issue.


chore: add domain and repository mappings for LunaSea

This adds a repository/domain mapping for https://github.com/JagandeepBrar/LunaSea.
The DNS record is currently pointing to the old documentation site, but will be switched once this PR is merged to prevent minimal downtime (if it needs to be switched beforehand, please let me know).

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Add Github Greeting Bot

Hey 🥳 Looks like an amazing project idea! I see this repo lacks a small enhancement Github Greetings bot that sends auto messages to greet new users when they raise a PR or an issue. Let me know if you would like this level1 set up! Please assign to me if interested! (GSSoC24 Contribution)

@KiranBaliga  I am mentor of this repo try to raise issues , after get response from the PA , I will assign it

@KiranBaliga Do ahead and make it quick

@Sibam-Paul I have raised the PR..Please review. Thank you!


Android - share limited to open channels/users

Environment Information

Mattermost App Version: 1.15.2
Mattermost Server Version: 5.7.0

Steps to reproduce
Share an image from gallery app
Expected behavior
Press channel, see open channels/chats, use the input field to search for ALL channels/users, choose one/any channel/user on the team that you can access
Observed behavior
Search field can search only open channels/users

Closing this as there is now a Help Wanted ticket open for this (linked above).


use system tmp folder

Hi,
as I am not sure what you think about it I wanted to discuss this before creating a PR:
I would suggest to use ioutil.TempFile https://gobyexample.com/temporary-files-and-directories as it's the preferred way to create tmp files in Go.
What do you think?

Hi @aligator, I think keeping the existing method of tmp folder allocation is a better decision then using the Golang build-in one. Here are twp points that I think are important.

ArozOS and SlicerA are both designed to be usable on low power ARM based single board computers (SBCs). Some of the SBCs have as little as 512MB RAM which makes the /tmp folder not have enough space to buffer a large STL file. ( I have used the ioutil.TempFile method in ArozOS on those SBC before and this was what I concluded as the best approach to buffer a large file in these type of embedded systems)
Future updates might allow us to set the tmp folder location with startup flags to different drives (e.g. if you are deploying on cloud VM for example) if we keep the current implementation.

In summary, I will be suggesting that we can keep this part first and in future updates, we can allow user to define their own tmp folder location if needed. Do you think this will be a better approach?

Ah ok, I see. The only thing I can think of would be to just use the ioutil.TempFile in the standalone mode only.
But yes, for now it's ok.
Maybe we just leave this ticket open until we know how to handle it better?

I have added the custom flags for allowing user defined tmp folder.
To use it, start SlicerA with the -tmp flag. Here is an example,
./SlicerA -tmp "/tmp"

Then all tmp files will be buffered to the system /tmp folder (which is the same as the place where ioutil buffers its temp files). Or otherwise, leave it as default for generating as the SlicerA's root folder.
I guess this is good enough for now. Let me know if you have other thought and I will re-open the issue if needed. Thanks!


Docker compose up exit code 217

Make sure these boxes are checked before submitting your issue - thank you!

[X] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[X] I have reproduced the issue with at least the latest released version of superset.
[X] I have checked the issue tracker for the same issue and I haven't found one similar.

Superset version
Lastest commit on master
Expected results
Docker compose working
Actual results
$ docker-compose up
superset_postgres_1 is up-to-date
superset_redis_1 is up-to-date
Creating superset_superset_1 ... done
Attaching to superset_postgres_1, superset_redis_1, superset_superset_1
superset_1  | + '[' 0 -ne 0 ']'
superset_1  | + '[' development = development ']'
superset_1  | + celery worker --app=superset.sql_lab:celery_app --pool=gevent -Ofair
superset_1  | + cd superset/assets/
superset_1  | + npm ci
postgres_1  | 2019-02-07 15:41:55.069 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
postgres_1  | 2019-02-07 15:41:55.069 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres_1  | 2019-02-07 15:41:55.109 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1  | 2019-02-07 15:41:55.235 UTC [22] LOG:  database system was shut down at 2019-02-07 15:31:58 UTC
postgres_1  | 2019-02-07 15:41:55.249 UTC [1] LOG:  database system is ready to accept connections
postgres_1  | 2019-02-07 15:42:51.678 UTC [30] ERROR:  duplicate key value violates unique constraint "ab_user_username_key"
postgres_1  | 2019-02-07 15:42:51.678 UTC [30] DETAIL:  Key (username)=(admin) already exists.
postgres_1  | 2019-02-07 15:42:51.678 UTC [30] STATEMENT:  INSERT INTO ab_user (id, first_name, last_name, username, password, active, email, last_login, login_count, fail_login_count, created_on, changed_on, created_by_fk, changed_by_fk) VALUES (nextval('ab_user_id_seq'), 'admin', 'user', 'admin', 'pbkdf2:sha256:50000$fgf6eYlb$bb1e6c1f420de4d894f7a917a72712c0b846dd969f51afb7cf386f0848508422', true<EMAIL_ADDRESS>NULL, NULL, NULL, '2019-02-07T15:42:51.677213'::timestamp, '2019-02-07T15:42:51.677242'::timestamp, NULL, NULL) RETURNING ab_user.id
redis_1     | 1:C 07 Feb 15:41:55.444 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1     |                 _._
redis_1     |            _.-``__ ''-._
redis_1     |       _.-``    `.  `_.  ''-._           Redis 3.2.12 (00000000/0) 64 bit
redis_1     |   .-`` .-```.  ```\/    _.,_ ''-._
redis_1     |  (    '      ,       .-`  | `,    )     Running in standalone mode
redis_1     |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
redis_1     |  |    `-._   `._    /     _.-'    |     PID: 1
redis_1     |   `-._    `-._  `-./  _.-'    _.-'
redis_1     |  |`-._`-._    `-.__.-'    _.-'_.-'|
redis_1     |  |    `-._`-._        _.-'_.-'    |           http://redis.io
redis_1     |   `-._    `-._`-.__.-'_.-'    _.-'
redis_1     |  |`-._`-._    `-.__.-'    _.-'_.-'|
redis_1     |  |    `-._`-._        _.-'_.-'    |
redis_1     |   `-._    `-._`-.__.-'_.-'    _.-'
redis_1     |       `-._    `-.__.-'    _.-'
redis_1     |           `-._        _.-'
redis_1     |               `-.__.-'
redis_1     |
redis_1     | 1:M 07 Feb 15:41:55.446 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1     | 1:M 07 Feb 15:41:55.446 # Server started, Redis version 3.2.12
redis_1     | 1:M 07 Feb 15:41:55.446 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1     | 1:M 07 Feb 15:41:55.446 * DB loaded from disk: 0.000 seconds
redis_1     | 1:M 07 Feb 15:41:55.446 * The server is now ready to accept connections on port 6379
superset_1  | npm WARN prepare removing existing node_modules/ before installation
superset_1  | npm ERR! path /home/superset/superset/assets/node_modules/core-js/fn/array/virtual
superset_1  | npm ERR! code ENOTEMPTY
superset_1  | npm ERR! errno -39
superset_1  | npm ERR! syscall rmdir
superset_1  | npm ERR! ENOTEMPTY: directory not empty, rmdir '/home/superset/superset/assets/node_modules/core-js/fn/array/virtual'
superset_1  |
superset_1  | npm ERR! A complete log of this run can be found in:
superset_1  | npm ERR!     /home/superset/.npm/_logs/2019-02-07T15_47_06_436Z-debug.log
postgres_1  | 2019-02-07 15:47:06.572 UTC [36] LOG:  unexpected EOF on client connection with an open transaction
superset_1  | npm WARN prepare removing existing node_modules/ before installation
superset_1  | npm ERR! path /home/superset/superset/assets/node_modules/core-js/fn/array/virtual
superset_1  | npm ERR! code ENOTEMPTY
superset_1  | npm ERR! errno -39
superset_1  | npm ERR! syscall rmdir
superset_1  | npm ERR! ENOTEMPTY: directory not empty, rmdir '/home/superset/superset/assets/node_modules/core-js/fn/array/virtual'
superset_1  |
superset_1  | npm ERR! A complete log of this run can be found in:
superset_1  | npm ERR!     /home/superset/.npm/_logs/2019-02-07T15_50_51_169Z-debug.log
postgres_1  | 2019-02-07 15:50:51.297 UTC [44] LOG:  unexpected EOF on client connection with an open transaction
superset_superset_1 exited with code 217
superset_1  | npm WARN prepare removing existing node_modules/ before installation
superset_1  | npm ERR! path /home/superset/superset/assets/node_modules/core-js/fn/array/virtual
superset_1  | npm ERR! code ENOTEMPTY
superset_1  | npm ERR! errno -39
superset_1  | npm ERR! syscall rmdir
superset_1  | npm ERR! ENOTEMPTY: directory not empty, rmdir '/home/superset/superset/assets/node_modules/core-js/fn/array/virtual'
superset_1  |
superset_1  | npm ERR! A complete log of this run can be found in:
superset_1  | npm ERR!     /home/superset/.npm/_logs/2019-02-07T15_54_35_445Z-debug.log
postgres_1  | 2019-02-07 15:54:35.595 UTC [52] LOG:  unexpected EOF on client connection with an open transaction
superset_superset_1 exited with code 217
superset_1  | npm WARN prepare removing existing node_modules/ before installation
superset_1  | npm ERR! path /home/superset/superset/assets/node_modules/core-js/fn/array/virtual
superset_1  | npm ERR! code ENOTEMPTY
superset_1  | npm ERR! errno -39
superset_1  | npm ERR! syscall rmdir
superset_1  | npm ERR! ENOTEMPTY: directory not empty, rmdir '/home/superset/superset/assets/node_modules/core-js/fn/array/virtual'
superset_1  |
superset_1  | npm ERR! A complete log of this run can be found in:
superset_1  | npm ERR!     /home/superset/.npm/_logs/2019-02-07T15_58_19_852Z-debug.log
postgres_1  | 2019-02-07 15:58:19.963 UTC [61] LOG:  unexpected EOF on client connection with an open transaction
superset_superset_1 exited with code 217
superset_1  | npm WARN prepare removing existing node_modules/ before installation
superset_1  | npm ERR! path /home/superset/superset/assets/node_modules/core-js/fn/array/virtual
superset_1  | npm ERR! code ENOTEMPTY
superset_1  | npm ERR! errno -39
superset_1  | npm ERR! syscall rmdir
superset_1  | npm ERR! ENOTEMPTY: directory not empty, rmdir '/home/superset/superset/assets/node_modules/core-js/fn/array/virtual'
superset_1  |
superset_1  | npm ERR! A complete log of this run can be found in:
superset_1  | npm ERR!     /home/superset/.npm/_logs/2019-02-07T16_02_04_350Z-debug.log
postgres_1  | 2019-02-07 16:02:04.473 UTC [69] LOG:  unexpected EOF on client connection with an open transaction
superset_superset_1 exited with code 217
superset_1  | npm WARN prepare removing existing node_modules/ before installation
superset_1  | npm ERR! path /home/superset/superset/assets/node_modules/core-js/fn/array/virtual
superset_1  | npm ERR! code ENOTEMPTY
superset_1  | npm ERR! errno -39
superset_1  | npm ERR! syscall rmdir
superset_1  | npm ERR! ENOTEMPTY: directory not empty, rmdir '/home/superset/superset/assets/node_modules/core-js/fn/array/virtual'
superset_1  |
superset_1  | npm ERR! A complete log of this run can be found in:
superset_1  | npm ERR!     /home/superset/.npm/_logs/2019-02-07T16_05_48_096Z-debug.log
postgres_1  | 2019-02-07 16:05:48.222 UTC [78] LOG:  unexpected EOF on client connection with an open transaction
superset_superset_1 exited with code 217
superset_1  | npm WARN prepare removing existing node_modules/ before installation

Note that the execution started on  2019-02-07 15:41:55.069 and the "screenshot" was taken on  2019-02-07 16:05:48.222 without any result. It seems that it is always repeating the:
superset_1  | npm WARN prepare removing existing node_modules/ before installation
superset_1  | npm ERR! path /home/superset/superset/assets/node_modules/core-js/fn/array/virtual
superset_1  | npm ERR! code ENOTEMPTY
superset_1  | npm ERR! errno -39
superset_1  | npm ERR! syscall rmdir
superset_1  | npm ERR! ENOTEMPTY: directory not empty, rmdir '/home/superset/superset/assets/node_modules/core-js/fn/array/virtual'
superset_1  |
superset_1  | npm ERR! A complete log of this run can be found in:
superset_1  | npm ERR!     /home/superset/.npm/_logs/2019-02-07T16_05_48_096Z-debug.log
postgres_1  | 2019-02-07 16:05:48.222 UTC [78] LOG:  unexpected EOF on client connection with an open transaction
superset_superset_1 exited with code 217

Steps to reproduce
I followed these steps: https://github.com/apache/incubator-superset/blob/master/docs/installation.rst
based on that commit 823555e

Don't know why and how but the error has disappeared :/


Implement atoms

We need to implement all the atoms with the same functionality

@maxonfjvipon 25 puzzles #10, #11, #12, #13, #14, #15, #16, #17, #18, #19, #20, #21, #22, #23, #24, #25, #26, #27, #28, #29, #30, #6, #7, #8, #9 are still not solved.

@maxonfjvipon 24 puzzles #10, #11, #12, #13, #14, #15, #16, #17, #18, #19, #20, #21, #22, #23, #24, #25, #26, #27, #29, #30, #6, #7, #8, #9 are still not solved; solved: #28.

@maxonfjvipon 24 puzzles #40, #41, #42, #43, #44, #45, #46, #47, #48, #49, #52, #53, #54, #55, #56, #57, #58, #59, #60, #61, #62, #63, #64, #65 are still not solved.

@maxonfjvipon 25 puzzles #40, #41, #42, #43, #44, #45, #46, #47, #48, #49, #52, #53, #54, #55, #56, #57, #58, #59, #60, #61, #62, #63, #64, #65, #71 are still not solved.

@maxonfjvipon 12 puzzles #40, #52, #53, #54, #57, #58, #59, #60, #61, #62, #71, #73 are still not solved; solved: #41, #42, #43, #44, #45, #46, #47, #48, #49, #55, #56, #63, #64, #65.

@maxonfjvipon 8 puzzles #40, #57, #58, #62, #71, #73, #76, #77 are still not solved; solved: #41, #42, #43, #44, #45, #46, #47, #48, #49, #52, #53, #54, #55, #56, #59, #60, #61, #63, #64, #65.

@maxonfjvipon 7 puzzles #57, #58, #62, #71, #73, #76, #77 are still not solved; solved: #40, #41, #42, #43, #44, #45, #46, #47, #48, #49, #52, #53, #54, #55, #56, #59, #60, #61, #63, #64, #65.

@maxonfjvipon 11 puzzles #109, #110, #111, #112, #113, #114, #117, #118, #62, #76, #77 are still not solved; solved: #40, #41, #42, #43, #44, #45, #46, #47, #48, #49, #52, #53, #54, #55, #56, #57, #58, #59, #60, #61, #63, #64, #65, #71, #73.


Extract Config

The class Config is made on the basis of BuildOptions.

@sv99 - may you handle conflicts?

PR rebased

Most changes trivial. Some fields moved from Androlib to the Config because its configuration properties.
I have next PR in which I move build function from Androlib to the new class ApkBuilder and decode function in the existing class ApkDecoder with some API unifications.

You can see result in my fork https://github.com/sv99/Apktool

I correct most corrected of the comments.

Still looking at this. Haven't forgotten about it.

thanks. merged - https://github.com/iBotPeaches/Apktool/commit/10495cbe966e6fb909324c8abf6148cbb009ed3c


Render function not defined error

Just added everything as per instructions (installed summernote), getting this error:

Failed to mount component: template or render function not defined.

found in

---> <VueHtmlEditor>

Same error!

Same error!

Anyone manage to resolve this?

Same error here

Same error!


Add a method to write a link name without canonicalization

In https://github.com/ostreedev/ostree we generate a cryptographic
checksum over files and symlinks, and directories.
ostree does not currently perform any canonicalization on symlinks;
we'll respect and honor whatever bytes we're provided as input,
and replicate that on the target.
I'm using this crate to do tar serialization, which has so far worked
fine...except, I hit this corner case:
[root@cosa-devsh ~]# rpm -qf /usr/lib/systemd/systemd-sysv-install
chkconfig-1.13-2.el8.x86_64
[root@cosa-devsh ~]# ll /usr/lib/systemd/systemd-sysv-install
lrwxrwxrwx. 2 root root 24 Nov 29 18:08 /usr/lib/systemd/systemd-sysv-install -> ../../..//sbin/chkconfig
[root@cosa-devsh ~]#

But, using set_link_name to write the tarball, we end up with
the canonicalized path ../../../sbin/chkconfig - i.e. without the
double //.  This breaks the checksum.
Now, I am a bit tempted to change ostree to do canonicalization.  But
even if we did, I'd need to exactly match what this crate is doing.
In the end, what I think is useful here is a method which skips
the canonicalization and internal error checking and just writes
out into the tar stream what's requested.
(I may of course also try to change the rhel8 systemd package, but
that's going to take a while to propagate and this corner case isn't
the only one I'm sure)

At a higher level, there's obviously a spectrum here around:

Friendly high level library that provides useful errors if you e.g. try to add obviously broken things into a tarball, and cleans up paths etc.
Medium level library that will allow writing valid tarballs
Low level library that would allow writing even corrupted tarballs

I'd say probably this crate doesn't need to go to the low level, but unfortunately because tar is so pervasive and so old, I think there's a need for the "medium level" to ensure we can handle all sorts of (valid but not necessarily canonical) cases.

Also, the astute reader here will note that I actually just wrote a different PR around symlinks: https://github.com/alexcrichton/tar-rs/pull/273
And so the question arises - do we need to handle long and non-canonical symlink targets?  As of right now, I don't need it.  But it could make sense.

Seems reasonable to me! Given that this is a raw thing though perhaps this method could take T: AsRef<[u8]> instead to be clear it's just shipping bytes from one location to another?

Given that this is a raw thing though perhaps this method could take T: AsRef<[u8]> instead to be clear it's just shipping bytes from one location to another?

Good point; done!

After this merges; when you have a chance a new release of this crate would be nice!


[Usersnap] Treasury withdrawal shown clearly

Why
Because it is currently not shown very well
What
The amount and destination address of the withdrawal
How
Just show it

This feature is planned for the next release.


[Question] How do I change via snippet.css the backgrond color of the table header?

Describe the bug
I'm sorry to ask, but how do I change the background color of the table headers and the cell text color via snippet.css?
Could you give me an example or point me in the right direction?
TIA
Steps to reproduce
none
Expected behavior
none
Are you using the mobile app?
Yes
Obsidian debug info
none
Relevant log output
No response

@BobWs Hi Bob. The selector you would use would be
.NLT__app th {
   background-color: <your-color-here>
}

Would it be easier if I were to add back a class name for the header? Like .NLT__th?

See the "CSS Styling" section of the README for more selectors. https://github.com/trey-wallis/obsidian-notion-like-tables#css-styling

@BobWs I have added some additional documentation. Please see: https://trey-wallis.github.io/obsidian-notion-like-tables/#/guide-snippet

@trey-wallis Thank you! ☺

links dead...


Progress bar screen disappeared for schemas.

Problem description
If user tries upload/publish any schema, he doesn't see progress bar of uploading/publishing anymore.
Step to reproduce
Steps to reproduce the behavior:

Create schema and save it / or import schema / or publish existing schema

Expected behavior
Progress bar appeared, after that list if schemas are updates, new schema is presented
https://images.zenhubusercontent.com/416030891/06a1a9f5-3e6c-41be-9c39-024a393278b4/screen_recording_2023_04_24_at_9_56_49_am.mov
Actual behavior
There is no progress bar, list of schemas aren't updated, new schema isn't presented. To see new schema/ new status of schema (draft -> published) you need to update the page.

duplicate of #2046 ticket


Misc. doc tweaks

Some of these changes could be considered "errors", like the long section titles which break the Table of Contents:

But others are debatable ... so feel free to ignore the changes you don't agree with. Thanks!

At the end, my english seems not too bad :) Thank you!


Document Playbook Upgrade Steps

There are times when we make modifications to the template which can cause previously generated variables to fail.

Document steps in README.md for upgrades (e.g. git pull, create new template, copy over, etc...)

We sort of have this now.


Revised TypeScript declaration

added $.term.syntax function (provided by prism)
added height option to Terminal instance (as it should be)
fixed several typos
lint the file

Beside this question, it looks good. Thanks for the fix.

I really need to fix the broken test ASAP, (there is one typescript check that validate d.ts file, it don't run because of previous errors) probably will do at the weekend.


Change to multi-strategy tenant sourceidentifier lookups

Summary
Due to the need for a more flexible solution, the tenancy resolution system is structurally changed from accepting one resolver to accepting a list of resolvers.
Changed

Changed the tenancy resolution system to support multiple methods pr. request, so that if one method fails another can catch it.

Reviewed with Einar.


Allow prerender routes to presist headers

This requirement was discovered from https://github.com/Baroshem/nuxt-security/issues/335 > https://github.com/Baroshem/nuxt-security/blob/main/src/runtime/nitro/plugins/05-cspSsgPresets.ts
This module particularly requires to presist CSP headers (using route rules was initial workaround but hacky) so that when site is pre-rendered, they still work.
Main thing to discuss is when we do it:

Behind an experimental flag and eventually always all headers
Using a new X-add-* convention
Using a global option

Would this issue also track the persistence of content-type headers for generated xml/json data?


JExcel + JSuites dropdown hidden in scrolling datagrid (+hacky fix)

While building a prototype jexcel grid that scrolls horizontally I came across an issue where when the jquites dropdown were hidden by the overflow. I implemented a hacky fix in jsuites.js that fixes it for us in jExcel, but it uses hardcoded element id's. I'm sure Paul could code a better solution, but it works for my purposes.
There's a video explanation here:
https://www.screencast.com/t/qunU3ESUu1
And the adjusted code in jsuites.js from line 2444 is
// #mod get jexcel datagrid
var grid = document.getElementById("maintool").querySelectorAll(".jexcel_content");

if (window.innerHeight < rect.bottom + rectContainer.height) {
	container.style.top = (-1 * (rectContainer.height)) + 'px';
} else if(typeof(grid) !== 'undefined' && grid[0].offsetHeight - 100 < rect.bottom + rectContainer.height){
	// if inside a scrolling grid make dropdown expand up.
	container.style.top = (-1 * (rectContainer.height)) + 'px';
} else{
	container.style.top = '';
}

This is using a hardcoded #maintool CSS id, so isn't really generic enough for all uses and no doubt could be improved.

thanks


API dependency missing in pkg-config

API dependency on ml-api-common is missing in pkg config.

:octocat: cibot: Thank you for posting issue #1250. The person in charge will reply soon.


Remove usage of testWidgetsWithLeakTracking.

Usage of testWidgetsWithLeakTracking should be removed in order to integrate leak tracking with testWidgets.
If testWidgetsWithLeakTracking coexists with the integration, it creates circular reference between leak_tracker and testWidgets, that we do not want.
Contributes to https://github.com/flutter/flutter/issues/135856

Bypassed google3 testing, because status is no test needed and update of status fails.


Using user_bowtie

Hi,
I am trying to assemble chloroplast from my raw WGS data. I would like to use my own reference genome, how can I use it as user_bowtie?

You need to create the Bowtie2 indices yourself and give then path for them with the --user_bowtie option.
Best,
Michael


Parent class for Stack and Chain

There are a lot of way stack and chain objects are similar, and a lot of utility/convenience functions that are useful for both (and not useful to much else).
Examples include the following methods:
stack.describe()
stack.verify_key_types()
stack.verify_multiple_key_types()
stack.verify_key_exists()
stack.force_key_as_list()
stack.yield_links()
stack.yield_views()
stack.reduce()
stack.save()
stack.load()

... and the following function (there are more....):
core.tools.view.query.get_dataframe

... and over time, no doubt many more.
What would be better is a new Class that defines all of these similarities and from which both Stack and Chain (and probably other 'shape' variants in the future) inherit.

@biggihs this seems like a good fit for you, when we get to it.

I guess we can close this @jamesrkg ?


Move to poetry

This moves the packaging and dependency management to poetry.
Allows it to be installable by github repo. (No published pip package yet).
Like did-tdw = { git = "https://github.com/bcgov/trustdidweb-py.git" }.
Then a project like aca-py can import did_web and did_history packages.

Looks good! It might simplify things to move the did_history package into did_tdw.history if you think that's worthwhile. I kept them separate in case the log handling was useful for other methods, but that can be split off into a separate package later if it's needed.


Check for config.json by default

Can we have the option to not use a query param and just look for config.json by default?
I'd like to create a subdomain to use with this project, but don't want users to have to remember to add params every time.
An ENV Variable to set the path to a file would work as well.  I don't see one documented.

Duplicates #222


Zend_Http_Client keeps adding the same get params when config strictredirects = true

When the client config strictredirects is set to true, the get params are added again to the uri after following the redirects.
request 1:
GET http://www.domain.com?test=test
response 1:
301 permanent redirect
request 2:
GET http://www.domain.com?test=test&test=test
Request 2 should be:
GET http://www.domain.com?test=test
This can be solved by replacing line 1058 (https://github.com/zendframework/zf1/blob/master/library/Zend/Http/Client.php#L1058) with:
if ($this->redirectCounter == 0) {
     $uri->setQuery($query);
}

I wasn't able to reproduce this. Could you elaborate how exactly the 301 redirect in "response 1" should look like, @jeffreylasut ?


add with_timezone

Which issue does this PR close?

Closes #5905
Rationale for this change

What changes are included in this PR?

a new function with_timezone that replace the timezone of timestamp without changing underline value
❯ select WITH_TIMEZONE(timestamp '2000-01-01T00:00:00.123456789', '+08:00');
+--------------------------------------------------------------------+
| withtimezone(Utf8("2000-01-01T00:00:00.123456789"),Utf8("+08:00")) |
+--------------------------------------------------------------------+
| 2000-01-01T08:00:00.123456789+08:00                                |
+--------------------------------------------------------------------+
1 row in set. Query took 0.004 seconds.

❯ select WITH_TIMEZONE(WITH_TIMEZONE(timestamp '2000-01-01T00:00:00.123456789', '+08:00'), '+07:00');
+-------------------------------------------------------------------------------------------------+
| withtimezone(withtimezone(Utf8("2000-01-01T00:00:00.123456789"),Utf8("+08:00")),Utf8("+07:00")) |
+-------------------------------------------------------------------------------------------------+
| 2000-01-01T07:00:00.123456789+07:00                                                             |
+-------------------------------------------------------------------------------------------------+
1 row in set. Query took 0.003 seconds.

while the timezone is incorrect, it raises error
❯ select WITH_TIMEZONE(timestamp '2000-01-01T00:00:00.123456789', '+25:00');
Arrow error: Parser error: Invalid timezone "+25:00": '+25:00' is not a valid timezone

Are these changes tested?

yes, test cases are added to timestamps.slt
Are there any user-facing changes?

Thanks @waitingkuo --
Even though arrow_cast could (and probably should) be updated to support timezones having a specific WITH_TIMEZONE seems like a good idea to me as it will be a better experience
I think this PR needs

Get the type correct (I left a comment about how to do this)
Add an entry to WITH_TIMEZONE the user documentation (e.g. https://github.com/apache/arrow-datafusion/blob/f00ef9d5484039dc7013af5b8fa04f7b29ffaba7/docs/source/user-guide/sql/scalar_functions.md?plain=1#L1208
)

Hi @alamb thanks, in fact i'm working on adding timezone support for arrow_cast now, will send a pr soon

In fact i'm working on adding timezone support for arrow_cast now, will send a pr soon

I think we may want to fix https://github.com/apache/arrow-rs/issues/1936 upstream, before exposing the currently incorrect timezone casting behaviour in arrow-rs?

Thanks @waitingkuo --
Even though arrow_cast could (and probably should) be updated to support timezones having a specific WITH_TIMEZONE seems like a good idea to me as it will be a better experience
I think this PR needs

Get the type correct (I left a comment about how to do this)
Add an entry to WITH_TIMEZONE the user documentation (e.g. https://github.com/apache/arrow-datafusion/blob/f00ef9d5484039dc7013af5b8fa04f7b29ffaba7/docs/source/user-guide/sql/scalar_functions.md?plain=1#L1208
)

Hi @alamb  thank you for the suggestion.
does it mean that i need to move WITH_TIMEZONE out of BuiltinScalarFunction ?

does it mean that i need to move WITH_TIMEZONE out of BuiltinScalarFunction ?

I am not sure to be honest -- there might not be a good existing pattern to follow for such functions. :tin

@alamb thanks, i'll think about how to fix this

Since this has been open for more than a year, closing it down. Feel free to reopen if/when you keep working on it.


Update fs2-io to 3.2.4

Updates co.fs2:fs2-io from 3.2.2 to 3.2.4.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "co.fs2", artifactId = "fs2-io" } ]

labels: test-library-update, early-semver-patch, semver-spec-patch, commit-count:1

Codecov Report

Merging #109 (0591fad) into master (d5cd0cb) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #109   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines            9         9
=========================================
  Hits             9         9

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 dc0bfe0...0591fad. Read the comment docs.

Superseded by #116.


Some comment signatures show invalid

I'll try to repro this, but a comment from last week had an invalid signature for a channel that was never updated(only way a signature can get invalidated).  @osilkin98 please take a look to see if anything if obvious about this one.
lbrynet comment list --claim_id=2a4f9d71111b1d110ee42e8aa17e5c007022ab1c
      "channel_id": "f2f1b9e5beb7bde033f0c4dd1dd87537bb95e373",
      "channel_name": "@testsssss",
      "channel_url": "lbry://@testsssss#f2f1b9e5beb7bde033f0c4dd1dd87537bb95e373",
      "comment": "infinite patience",
      "comment_id": "5f43cb1a711c6bab1688c3e190fa2ad31c903cb542688accda7c6b8e878b7ee5",
      "is_channel_signature_valid": false,
      "signature": "33ef44d99e30c8eedade272ef4f81000fbe632ddd1bf3d957a9954dd47ad1017",
      "timestamp":<PHONE_NUMBER>
    },

(lbry-venv) C:\Users\thoma\Documents\lbry>lbrynet resolve @testsssss#f2f1b9e5beb7bde033f0c4dd1dd87537bb95e373
{
  "@testsssss#f2f1b9e5beb7bde033f0c4dd1dd87537bb95e373": {
    "address": "bSS16SZAJdvSVz1ACQoxd8JQKXaWF6xDSS",
    "amount": "0.001",
    "canonical_url": "lbry://@testsssss#f",
    "claim_id": "f2f1b9e5beb7bde033f0c4dd1dd87537bb95e373",
    "claim_op": "create",
    "confirmations": 6885,
    "height": 584448,
    "meta": {
      "activation_height": 584448,
      "claims_in_channel": 0,
      "creation_height": 584448,
      "creation_timestamp":<PHONE_NUMBER>,
      "effective_amount": "0.001",
      "expiration_height": 2686848,
      "is_controlling": true,
      "support_amount": "0.0",
      "take_over_height": 584448,
      "trending_global": 0.0,
      "trending_group": 0,
      "trending_local": 0.0,
      "trending_mixed": 0.0
    },
    "name": "@testsssss",
    "normalized_name": "@testsssss",
    "nout": 0,
    "permanent_url": "lbry://@testsssss#f2f1b9e5beb7bde033f0c4dd1dd87537bb95e373",
    "short_url": "lbry://@testsssss#f",
    "timestamp":<PHONE_NUMBER>,
    "txid": "05451dcd09bc56140dd9859ffa68e0d612c50186dea734273ab8d84435d9a949",
    "type": "claim",
    "value": {
      "public_key": "3056301006072a8648ce3d020106052b8104000a034200049c291b48926e5e49f312311e9ad2c684e3b4128488a9650005cea7f4e3f754313a9de0298a1e4701c74519566ca2f2c348c6f2782c077c5d087bc5d889c45c39",
      "public_key_id": "bKPd8h9arHVYFauT7HED7djVNkRyXAvdQr"
    },
    "value_type": "channel"```

@osilkin98 can you check the comment server to see how many are valid vs invalid? I think this was an issue from early testing.

@tzarebczan
Total Signatures: 457
Valid Signatures: 348
Invalid Signatures: 109
Percent Valid: 76.149%

Are the invalid ones anonymous, or actually invalid? If they are invalid, can you investigate?

@tzarebczan They're mostly just test comments, it seems. At least five different channels making the comments are unresolving.

Great, thanks for looking into that. Closing for now.


Touch up whitespace issue in build man

Signed-off-by: TomSweeneyRedHat<EMAIL_ADDRESS>Fixes a trailing whitespace in build man page that was causing git unhappiness.

I am going to force merge this since it is causing other issues. No code involved.


Change Function.prototype.toString() to be ES6 compatible

ES5.1 requirement is that Function.prototype.toString() result must be parseable as a FunctionDeclaration with no further requirements (it doesn't have to compile into an equivalent function, for instance).
ES6 changes this so that the source code must either parse to an equivalent function, or must else cause a SyntaxError in parsing. See comments starting from: https://github.com/svaarala/duktape/pull/1135#issuecomment-264617551.

[x] Change the .toString() behavior
[x] Update testcases
[x] Check Emscripten compatibility
[x] Migration notes
[x] Releases entry

Here's the current behavior in this branch, and a comparison to V8.
For a native function:
duk> String(Math.cos)
= "function cos() { [native code] }"

> String(Math.cos)
'function cos() { [native code] }'

So output for non-bound native functions is now the same.
For Ecmascript functions:
duk> String(function foo(a,b) { return a+b; })
= "function foo() { [ecmascript code] }"

> String(function foo(a,b) { return a+b; })
'function foo(a,b) { return a+b; }'

Here there's a natural difference as V8 provides the source. Duktape output won't eval() parse anymore, as required by ES6.
Bound functions behave differently:
duk> String(Math.cos.bind())
= "function bound cos() { [bound code] }"

> String(Math.cos.bind())
'function () { [native code] }'

The main difference is that V8 looks up the final non-bound function and shows its type (native or Ecmascript).  For some reason V8 also drops the function name, showing neither "cos" (the target function's .name) nor "bound cos" (the bound function's .name).
The current Duktape output re: function names is "broken" in the sense that invalid function names (like a space in the bound function case) are allowed. But that's actually OK because it just causes a SyntaxError earlier than the function body.
I think I'll change the bound function behavior so that the native/ecmascript type would be shown and the bound status of the function would be lost. However, with that behavior it'd make most sense to show the target function's (non-bound function, that is) .name in the result. In other words, String(Math.cos) and String(Math.cos.bind()) would have the same output.

V8 behavior for bound Ecmascript function is quite interesting and probably leaks a bit of the internals:
> func = function foo(a,b) { return a+b; };
[Function: foo]
> String(func)
'function foo(a,b) { return a+b; }'
> String(func.bind(null, 1))
'function () { [native code] }'

There are some suggestions here (linked by @fatcerberus earlier): http://www.2ality.com/2016/08/function-prototype-tostring.html.
Following that would mean that a function's name would be omitted unless it was an intrinsic, so that:
> (function foo() {}).bind(null).toString()
'function () { [native code] }'

There's no internal distinction between "intrinsic" names and other names now, so this approach isn't possible right now.

The way I read that proposal it seemed like it was just bound functions and native functions for which the name would be omitted.

Sure - but only because the proposal calls for actual source code to be returned for Ecmascript functions?
If that's not implemented, then something else must happen.

So if you take these two:

Whenever possible – source code: If a function was created via ECMAScript source code, toString() must return that source code. In ES2016, whether to do so is left up to engines.

Since that's not possible, at least right now:

Otherwise – standardized placeholder: In ES2016, if toString() could not (or would not) create syntactically valid ECMAScript code, it had to return a string for which eval() throws a SyntaxError. In other words, eval() must not be able to parse the string. This requirement was forward-incompatible – whatever string you come up with, you can never be completely sure that a future version of ECMAScript doesn’t make it syntactically valid. In contrast, the proposal standardizes a placeholder: a function whose body is { [native code] }. Details are explained in the next section.

So I would read this to mean Ecmascript functions would also use {  [native code] } if you weren't able to produce the source, so that a standardized placeholder is used.
The proposal of course has no bearing re: compliance, and I'd like to see directly from the function .toString() whether it's a native or a script function, even if source code wasn't available.
I'm not sure about bound functions though. If I had to choose, the current Duktape behavior is worse compared to looking up the target function and showing its type (hiding the bound status of the initial argument). Ideally both would be visible, but that's extra code and maybe not worth it.
A hybrid option would be to show the initial function's name but look up the native/Ecmascript type from the non-bound target. That way e.g. Math.cos.bind() would produce:
function bound cos() { [native code] }

which simultaneously indicates it's a bound function (via the required ES6 name), but also shows that the non-bound target is a native function. The downside is that the name looks funny (with the space) but that has no practical compliance impact because the whole thing is only required to eval() to SyntaxError. It doesn't matter that the SyntaxError comes from the function name rather than the function body.

Specifically what I don't like about the V8 behavior is this:
> (function foo() {}).bind(null).toString()
'function () { [native code] }'

The name is hidden, and "native code" sounds wrong from an Ecmascript target function.
I would Duktape to show at the very least:
function () { [ecmascript code] }

or more preferably include the name of the target:
function foo() { [ecmascript code] }

or maybe the name of the bound function (hybrid approach described above):
function bound foo() { [ecmascript code] }

The intent of the proposal, at least the way I read it, is that Ecmascript functions MUST carry source code.  Hence the bit that "in ES2016, whether to do so was left up to engines".
Like you said though, the proposal has no bearing on compliance, and I agree that it's weird to call an Ecmascript function "native code".  Anyway for ES6/7 compliance, the [ecmascript code] should be enough as all the spec requires right now is that it cause a SyntaxError.

The intent of the proposal, at least the way I read it, is that Ecmascript functions MUST carry source code. Hence the bit that "in ES2016, whether to do so was left up to engines".

Yes, I understood that :) But if you don't do that, the proposal still tries to say that "In contrast, the proposal standardizes a placeholder: a function whose body is { [native code] }.".
This is used for bound functions, even if they are Ecmascript functions. This is actually exactly what V8 does.
So, all I was saying is that this same approach could be used for bound functions in Duktape (or perhaps even Ecmascript functions). But that doesn't make much sense to me.

Re: that proposal document, note that it discusses two separate things. The first is a concrete proposal on what to return in each case. I'm not talking about that.
The second is about how the ES6 requirement of returning something that's a SyntaxError is actually rather ill-defined because there's no way to know what syntax is added down the line. So they propose a standard placeholder. And that placeholder is used whenever you don't produce an actual source. This placeholder still has relevance even if you don't follow the other parts of the proposal because of the forward-compatibility issue.
But in practical terms [native code], [ecmascript code], [bound code], and (currently) [lightfunc code] are similar enough to very likely be forward compatible enough. It's at least unlikely Duktape will accidentally change its own behavior without taking any future syntax into account :-) But it would theoretically matter if the .toString() output was parsed between versions or between engines.

Ah, I see what you mean now, sorry :)
Regarding V8's behavior for bound functions, I assume it doesn't return source code because that wouldn't meet the requirement of parsing to "a functionally equivalent object", so it just falls back on returning a SyntaxError-inducing stub.
I also remember reading somewhere in the specification that you're not supposed to reveal the target of a bound function, but I don't recall where I saw that now.

I also remember reading somewhere in the specification that you're not supposed to reveal the target of a bound function, but I don't recall where I saw that now.

I don't recall offhand either - that might make sense for the actual function reference. But since the bound function .name already reveals the target's name it'd be quite odd if the target type (native or not) would be off limits.

I'll merge this with the behavior above, specifically for bound functions:
function bound cos() { [bound code] }

That will fulfill the ES6 requirement and is analogous to what exists in master currently. This can be improved in follow-ups if there's a good, clear idea for e.g. bound functions.

Emscripten compatibility isn't affected by the change.

In regards to real-world usage of .toString() expecting to get actual function source code, I mentioned a few days ago that AngularJS did this, but didn't have a citation at the time beyond a passing mention in a SO question.  Well, here's an article talking about that:
http://perfectionkills.com/state-of-function-decompilation-in-javascript/

There are indeed real world code bases relying on function .toString() - I just find that quite awkward and prone to break when new language features are introduced.
But that's a topic for another pull: eventually Duktape should provide function source code too, but doing so is more than just tacking the compiler input as a property because of the variety of different syntaxes where functions may come from (object literal getters/setters, Function constructor, etc). So to make the source actually work, some processing is needed. That's the main reason I haven't yet implemented it.
Also for low memory targets it'd be nice if the source code could be compressed using some simple text-aware algorithm. Maybe bit packed like the built-in strings. It could then be expanded on request.

Interestingly, as mentioned in the comments of that article, SpiderMonkey used to reconstruct functions by decompiling then bytecode, but around FF 17 that was changed to just store the original source verbatim.  I think if anything were done in Duktape towards supporting this, that latter method would make most sense.
On the topic of this pull: It is apparently common to stringify bound functions as though they were native (the article mentions that too).  I prefer [bound code] personally, and from a practical standpoint, if [native code] will remain a SyntaxError going forward, substituting any other word in place of "native" will almost certainly remain so as well.

[...] around FF 17 that was changed to just store the original source verbatim. I think if anything were done in Duktape towards supporting this, that latter method would make most sense.

I never considered anything else than using the original source - doing otherwise would be a huge footprint impact because bytecode-to-source translation would be very expensive.
But the thing is, you can't just use the source because of the syntactic variants, so some processing is needed. It's not a huge undertaking though, just manufacturing a function expression around a plain body (which is already done to some extent by the Function constructor).

Opened #1147 for discussing the source code issue; it's out of scope for this pull.


Adding link to js-level-pull-blob-store

@dignifiedquire I found a way around the issue I was having with the tests.  Here is the link to the js-level-pull-blob-store.  Thanks for your help.

Great, thank you :octocat:


Error: Could not import 'main'.

flask run
 * Serving Flask app 'main' (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off
Usage: flask run [OPTIONS]

Error: Could not import 'main'.

Windows 10, Python 3.8. I did the installation of the requirements. I'm sort of a newb with flask but any ideas? Thanks!

Cancel this, it's because I wasn't running my command prompt as an administrator. Fixed. Thanks!


Incorrect error message "rbenv: version system is not installed" when calling non-existent system bundle command

This issue occurs where one project wants to use system ruby and another wants to use an rbenv specific version of ruby and bundler isn't installed for the system ruby.
Expected result
Given I have a system ruby installed
But I don't have the bundler gem installed for the system ruby
And I have a different version of ruby installed via rbenv
And I cd to a Rails 4 project
And that project has a .ruby-version file that specifies 'system' as the ruby to use
When I run "bundle install"
Then I should get the message "bundle: command not found"
Note: ruby -v in this project directory will appear to correctly state that system ruby is being used. The problem initially looks like this is not being propagated to the bundle command (which is the source of the confusion). That real problem being that bundler isn't installed for the system ruby.
Actual result
I get the message
rbenv: version `system' is not installed (set by RBENV_VERSION environment variable)

Workaround
This can be fixed by installing bundler for the system ruby...
rbenv shell system
gem install bundler # or sudo gem install bundler if neccessary
cd /to/your/rails4_project
bundle install # works!

Platform: Ubuntu with system ruby install via apt-get.
Potential solution: Perhaps in this case rbenv could check that the bundle command exists for system ruby - if not then say that in the error message.

Is this problem the same if you update rbenv to the latest version from master?
Try cd `rbenv root` && git pull origin master

Sorry, I can't reproduce this with newest version of rbenv. It must have been fixed in the meantime.

I am able to produce this - although I'm not sure how it could be handled better or whether it's a bug.
> which fluentd
/Users/pik/.rbenv/shims/fluentd
> rbenv local 2.1.0
> fluentd
rbenv: fluentd: command not found

The `fluentd' command exists in these Ruby versions:
  2.2.3

Which is correct, on the other-hand if one goes to a directory where rbenv does not have permissions to create .ruby-version file.
> cd /etc/fluent
> fluentd
rbenv: version `system' is not installed (set by RBENV_VERSION environment variable)

Thanks; I was able to reproduce the original invalid message now. I'll try to fix the message to say something like "the foo command doesn't exist in system paths".


Communication with Pleroma instances

Pleroma and Mastodon can work on same API data, so i am curious why i can't discover @user in my Pleroma instance? Even if i follow it from me.glitch.me there is no notification in Pleroma etc...

Huh! It is likely some issue with signature validation or some element of the headers provided, as this has caused issue with a few of the other apps.
I need to find a Pleroma instance to test against...


Set nokogiri version to 1.10.10

Set nokogiri version to 1.10.10 to fix issues when updating the gem from konekti

Closing this because we are going to set the nokogiri version on konekti since the ruby version there is limiting the nokogiri version

Closing this because we are going to set the nokogiri version on konekti since the ruby version there is limiting the nokogiri version


filter packages to instrument

To enhance fuzzing performance, we can limit coverage instrumentation
to packages that we want the fuzzer to explore. This way, the fuzzer
will focus on exploring the packages of interest. Otherwise, libfuzzer
will try to maximize coverage in all packages. This PR limit coverage
instrumentation to the packages explicitly configured by the -include
flag (default is include all packages) and not excluded by the
-preserve flag (default is none)

Thanks @AdamKorcz. Let me know if you have any remarks.

@AdamKorcz Any updates on this PR?


Re-enable BlackBoxOptim test

Right now it needed to be disabled since that package is completely unmaintained. Hopefully it comes back, in which case it can be re-enabled. It might be a good idea to fork it.

 GalacticOptim is on 1.1.0 and BBO on 0.5.0.

Yeah we need to get in touch with @robertfeldt to fix this. There hasn't been a tag on it since 2019 so the released version doesn't quite work. I would be happy to help out and keep it maintained because I love the library, but as is it just won't run.

Yes, I'm getting back to this lib more now. Will fix shortly. Master should be fine so will release that and delay other planned changes for now.

The warning about EnsembleOptimizationProblem stems from a previous PR which naively implemented an interface to the multiobjective optimizer BorgMOEA in BBO. I will make PR which removes/comments the old code until we have an EnsembleOptimizationProblem in SciMLBase rather than here.

I'm back to working on BBO, and recently released 0.6.0, so if there is something you need in relation to this please share. @ChrisRackauckas @jonasmac16
There are some known issues (like multi-threading support) being worked on but I'd like BBO to play nice with GalacticOptim. 0.6.0 supports giving an initial candidate solution but very limited testing as of yet so feedback welcome.

I think a batch interface for caller-side parallelism would be the main thing.

Thanks @ChrisRackauckas. I plan to do the API similar to Cubature.jl as you proposed previously. If you have other/better ideas please share.

That would be perfect.


Segmentation fault when registering mod sprites with mesa graphics driver

The fault occurs at i965_dri.so:__driDriverGetExtensions_nouveau_vieux+4BB96B.
This will require some more analysis, but it currently appears as if it's a sequencing issue.
The MRE normally registers sprites (along with all other resources) before the main game loop has started. With Nvidia and AMD graphics drivers, this works fine. With the mesa driver, however, this causes the segmentation fault. If the sprite registration period is moved to occur during the first step of the game loop, then no segmentation fault occurs, but the engine hangs for several seconds while loading the first sprite.
This leads me to believe the point at which the engine's sprite module is ready for use depends upon the graphics driver of the host system. When using Nvidia/AMD, the sprite module is ready long before the game-loop starts, but that's not the case with mesa.

Resolved by 08d3156b34442234778b5f38494f8b3e9790d524


removed unix timestamp option set

Q
A

Bug fix?
no

New feature?
no

Fixed tickets
#...

Removed unix timestamp option.

Codecov Report

Merging #1 (9716a3b) into main (5940282) will decrease coverage by 1.21%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@              Coverage Diff              @@
##                main       #1      +/-   ##
=============================================
- Coverage     100.00%   98.79%   -1.21%
+ Complexity        47       46       -1
=============================================
  Files             10       10
  Lines            170      166       -4
=============================================
- Hits             170      164       -6
- Misses             0        2       +2

Impacted Files
Coverage Δ

src/Weather/Infrastructure/AirQualityClient.php
93.54% <ø> (-6.46%)
:arrow_down:

src/AirQuality.php
100.00% <100.00%> (ø)


Media Queries

Create CSS media queries to make page accessible on phones/tablets

Media Query generated for:
mobile/small tablets
larger tablets/windowed browsers
full screen browsers
Merged:
https://github.com/PeaFunk3000/portfolio/pull/10


Initial Xtensa support

This PR adds the bare minimum Xtensa support to allow our Xtensa-enabled Rust fork to compile on stable 1.65, as we were running into https://github.com/rust-lang/rust/issues/102290 in our testing.

Please add this architecture to the elf_any test. #430 is a PR that did this for another architecture.

Thanks for the link to #430, was most helpful! I've gone ahead and implemented the relevant relocations for Xtensa and added the Xtensa arch to the test case as you requested.

Thanks, @philipc! Are there any plans to cut a new release anytime soon?

I'd like to do a release soon. However, there's a bit of XCOFF work in progress currently that I'd like to see polished a bit more first. I may consider doing a release with the XCOFF feature disabled somehow.


added code to HTML file

This PR adds all of the HTML we need for the prework study guid application